Skip to main content
Every tool reads, and each one is the twin of a single REST route: it reads through the same code, needs the same scope, and returns the same data, except that every string is cleaned of control and invisible characters and cut at 2,000 characters (see How data is handled). If a tool answers something, its route answers the same thing. There are no write tools. A connection made by signing in has every read scope. A key connection has the key’s scopes: a tool whose scope the key lacks is refused with 403 before it runs, naming the scope. When a tool cannot answer for another reason (a missing argument, an id that is not in your workspace, a report window that is too long), it says why in its result, so your assistant can correct the call and try again. The report tools (brands, domains and URLs) count as several requests against your rate limit, as their REST routes do. One that would go over your budget, or that is refused as busy because another report is running, answers with an error result naming rate_limited or busy rather than an HTTP 429 with Retry-After; wait a little and call it again. See Rate limits.

How data is handled

What the tools return, and what they never return.

Metric objects

The shape of every figure a tool returns.

API reference

The REST twin of each tool.

MCP overview

Connecting by sign-in or with a key.