A brief becomes a real page.Fix a catalog that is too large
Compare the full tool list with Compact mode using the same account and app.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- Access to the affected site and AI connection.
- A redacted copy of the exact error.
Let’s do this, step by step.
Step 01
Verify connection first
Confirm authentication and initialization work. Record the app, model, error, and other connected servers.
Only investigate a catalog limit after the connection itself works. A blank list can have several causes.
Step 02
Enable Compact mode
On the same WordPress site, open Tools, enable Compact tool mode, and save.
This changes the advertised list for all clients on the site. It keeps enabled actions available through three discovery and execution entry points.
Step 03
Reconnect the same app
Start a fresh connection or conversation and inspect the dispatcher tools.
Keep the endpoint and account the same so the comparison is useful. Multi-site routing tools may appear alongside the three EMCP tools.
Step 04
Test a read
Ask the AI to discover the page-listing action, inspect its inputs, and list real records.
If Compact mode works and the full catalog does not, you have evidence of a catalog-handling problem, not proof of an exact numeric cap.
Step 05
Keep the useful setting
Keep Compact mode if it fits the workflow, or investigate the app's documented limit with the captured evidence.
Disabled actions remain disabled. If both modes fail, return to connection diagnosis rather than trimming tools at random.
You’re done when…
You have comparable full/compact results and a working discovery route or a clear next diagnostic step.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.