project_id, which an agent gets from list_projects.
Every tool carries MCP annotations describing what it does, so a well-behaved client can prompt for confirmation selectively rather than on every call:
Tools marked write below change your account; quota means the call spends plan allowance. The protocol has no notion of cost, so billable tools are ordinary writes with the cost stated in their description — which is the only defence against an agent looping over a keyword list with a billable tool.
Onboarding
Start here.
list_projects gives the agent the project_id nearly everything else needs.
delete_project is the one tool annotated destructive. Everything it removes cascades and cannot be recovered.
Rank tracking
Tags are worth knowing about —
create_tag, list_tags, and assign_tags let an agent group keywords in ways the dashboard doesn’t surface as prominently.
Keywords
Backlinks
Audits
get_duplicate_content and get_broken_resources are dedicated tools that correspond to tabs in the audit detail view.
AI search
GEO
Domains and tech stack
Competitors
Local SEO
Web vitals
Trends
Content
generate_meta_tags and generate_content_brief have no dashboard equivalent — they’re only available through MCP.
Common arguments
organization — optional on org-scoped tools, taking a name or an id. Resolved automatically when you belong to exactly one organization. With several and none named, the call is refused and the error lists them; the server doesn’t guess. See choosing an organization.
project_id — required by most tools, obtained from list_projects. A project you can’t access returns “not found” rather than “not yours”, so a not-found isn’t proof of deletion.
Locale — tools taking one default to location 2840 (United States) and language en, matching the dashboard. If your project targets another market, tell the agent explicitly; it won’t infer the project’s locale for every call.
Your role applies
The OAuth token acts as you, so a tool can only do what your role permits. A member’s connection can’t calldelete_project; an owner’s can.
No token can mint an API key, change billing, invite or remove people, or reach an organization you’re not a member of — regardless of role.
Related
- MCP playbooks — prompts that use these well
- MCP authentication — the OAuth flow and what a session permits
- Usage and limits — the quota these draw on