Limits
| Limit | Value | What to do at the limit |
|---|---|---|
| Rows per call | 500 (50 by default) | Read the next page with offset. total_rows tells you how many there are. |
| Days per call | 90 | Ask for several periods. |
| Ad types per call | 1 | Call once per ad type. |
| Changes | none yet | Write tools are not live. See Read and write. |
Errors
There are two kinds, and they arrive differently.
A tool that cannot answer
The request itself succeeds, and the result says what to change. It has "isError": true and one sentence written for the AI to read, so most of the time your AI corrects itself and calls again.
{
"jsonrpc": "2.0",
"id": 3,
"result": {
"content": [{ "type": "text", "text": "One call covers at most 90 days. Ask for several periods to compare longer ones." }],
"isError": true
}
}
| Message | Cause |
|---|---|
date_from must be a date written as YYYY-MM-DD. (or date_to) | A date in another format, or one that does not exist. |
date_from is after date_to. | The period is the wrong way round. |
One call covers at most 90 days. Ask for several periods to compare longer ones. | The period is too long. |
You have 3 marketplaces. Say which one with marketplace_id (see list_accounts). | Several marketplaces on the plan and no marketplace_id. |
This marketplace is not part of your plan. Use list_accounts to see the ones that are. | A marketplace_id that is not yours or not switched on. |
No marketplace is part of your plan yet. | No marketplace is switched on in the dashboard. |
Say what to list with `type`: campaign, ad_group, keyword, target, negatives, product_ad, ad or portfolio. | get_structure without type. |
There is no tool called "…". | A tool name that does not exist. |
A tool can also return no rows with a note, for example when Amazon has no such report for the ad type. That is not an error.
A request the server refuses
These are HTTP and JSON-RPC errors. Your client reports them; the AI does not see a tool result.
| HTTP | JSON-RPC code | Meaning |
|---|---|---|
| 401 | -32001 | Missing or wrong API key. Create a key in the dashboard and use the address or command shown with it. |
| 405 | -32000 | A method other than POST. The server does not open a stream on GET. |
| 400 | -32700 | The body is not valid JSON. |
| 200 | -32601 | An unknown JSON-RPC method. |
| 200 | -32603 | Something went wrong on the server. Try again; if it repeats, the server has a fault. |
| 503 | -32000 | The server is not configured. This is on our side. |
An example:
{
"jsonrpc": "2.0",
"id": null,
"error": { "code": -32001, "message": "Missing or wrong API key. Create a key in the Adverso MCP dashboard and use the address or the command shown there." }
}