Errors & limits

Error format

Errors follow JSON-RPC 2.0. An error on tools/call has the form:

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": { "code": -32000, "message": "Short description of the error." }
}

Situation	What you see
Missing/invalid token	HTTP `401` with `WWW-Authenticate` → start OAuth (Authentication)
Wrong HTTP method on a connector endpoint	HTTP `405` (`Allow: GET, POST`)
Unknown tool or invalid arguments	JSON-RPC error with a descriptive `message`
Tool called without a subscription	The tool is not present in `tools/list` for your account

Validate arguments against the schemas in the API reference before calling — e.g. date format YYYY-MM-DD and rowLimit within 1–25000.

General (all connectors)

Upstream timeout: each upstream call is bounded at 15 seconds — a slow provider surfaces as an error rather than hanging.
Reconnect on revoke: a revoked or invalid upstream credential surfaces as a “reconnect required” error; reconnect the connector in the portal.

Google Search Console

Rows per request: up to 25,000 (limit / rowLimit).
Pagination: use startRow in search_analytics_query to fetch further.
Dates: always YYYY-MM-DD.
Properties: you can only reach properties your authorized Google account already has access to. Use list_sites to see them.

e-conomic

Page size: list tools take pagesize (default 20, max 1000) and skippages; not every list tool accepts filter/sort. See the e-conomic reference.

rowLimit and dataState below are Google Search Console-specific — they do not apply to the accounting connectors.

Search Console data is not real-time. The most recent days may be incomplete or missing because Google is still collecting them.

Expect a delay of a couple of days on the newest numbers.
In search_analytics_query you can control this with dataState:
- final — only fully collected data.
- all — includes preliminary (fresh but unstable) data.

Empty numbers usually mean the period has no data yet, or the selected property has no traffic in the range — not necessarily an error.