Skip to main content

How MCP works

Endpoint

Production serves the V2 Google Ads tool surface (top-level helpers + google_ads router).

What MCP gives you

AdCue exposes Google Ads operations as MCP tools so AI clients can:
  • Read account and campaign state
  • Create and manage Search campaigns (with safety rails)
  • Optimize keywords, budgets, and wasted spend
  • Reach advanced campaign types (Performance Max, YouTube, Demand Gen) when needed — marked advanced in the catalog
Tool names and counts come from the V2 registry export (docs-site/generated/tools.json). See the tool catalog for the full list. Do not hand-edit tool lists in narrative pages.

Router pattern

Most Google Ads operations go through the google_ads router. List tools:
Execute a tool:
Discovery helpers at the top level: Some tools are also available top-level (not only via the router). The catalog marks each name’s exposure as top, router, or both.

How a request flows

  1. You type a goal in the AI client (or call a tool directly).
  2. The client selects an AdCue tool and arguments.
  3. AdCue authenticates your session / token and loads the stored Google Ads connection.
  4. Read tools return data; write tools require product safety rules and your approval in the client.
  5. The client presents the result.

Safety (summary)

Full page: Safety model.

Advanced tools

A subset of tools for Performance Max, YouTube, and Demand Gen is flagged advanced in the generated catalog. Prefer core Search / account tools for everyday workflows unless you intentionally need those campaign types.