Skip to main content

​
Tool Reference overview

AdCue documents Google Ads operations as MCP tools, not as a public REST Ads API. There is no public REST base URL, versioned OpenAPI product contract, or SLA for a standalone HTTP Ads API in this documentation. Connect AI clients to the production MCP endpoint and call tools by name (or via the google_ads router).

​
Endpoint

​
What this section covers

​
How to call tools

Top-level tools (for example search_tools, get_connections_status) are called by name. Router tools use google_ads:
Some tools are available as both top-level and router (expose: both).

​
Safety (always)

  • Creates land PAUSED where the product applies that rule.
  • Destructive deletes require confirm_delete: true.
  • Budget fields that are skill-facing use dollars (decimal), not micros.
  • Prefer Search-first workflows; treat advanced campaign types as optional.
  • Runtime truth is live list_tools / get_tool_schema for your session — the static catalog can lag a deploy.
Full detail: Safety model.

​
Schema source

Per-tool pages are generated from docs-site/generated/tools.json (export of TOOL_SPECS). Do not hand-edit parameter tables on generated pages. Regenerate from a local google-ads-mcp checkout:

​
Out of scope

  • Meta, TikTok, LinkedIn, or other non-Google platform tools
  • Public REST Ads API base URLs or SLA claims
  • Full individual pages for every router tool (later batches expand Search and other groups)