The Ads copilot
What the copilot reads, what it proposes, and why it can never approve its own changes.
The Ads copilot is an agent with two kinds of tools: reads that inspect the warehouse and proposes that change the account. It runs in the account's AI Chat tab and, through the MCP bridge, from Claude Code or claude.ai. It grounds strategy in the optimization plan — pacing and CPA-vs-band — before suggesting anything.
Read tools are always safe
Reads never touch Google Ads with a write. They pull performance, inventory, change history, tracking health,
competitive pressure, audit findings, and the optimization plan straight from the synced warehouse. Examples:
gads_get_account_overview, gads_list_campaigns, gads_get_search_terms, gads_get_optimization_plan,
gads_run_gaql_query.
Propose tools are money-moving
Every write tool is named gads_propose_* and routes through one path: it never mutates live directly. It runs
a dry-run, gets classified by the safe-apply policy, and is either applied
automatically or queued for you. Coverage is broad — budgets, bids, keywords and negatives, RSAs and assets,
ad groups and campaigns, targets and bidding strategies, geo, device, and schedule modifiers, audiences, and
experiments.
Separation of duties
The in-app copilot proposes; it cannot approve. The approval tools
(gads_approve_action, gads_reject_action, gads_revert_action) exist only on the MCP bridge, where a
human is driving. So the copilot can never approve its own proposal — a decision is always yours.