← All agent use cases · Google ads use cases

A Claude Code hook that stops every Google Ads write until you approve it, on top of Google's MCP dry run

Google ads · Blog · · Shared by Thomas Wismer (Wismer Marketing)

Consultant Thomas Wismer tested the write tools in Google's official Google Ads MCP server (v0.0.6) in a live client account. Because the server only asks the AI to wait for a human before the confirming call, he added a Claude Code hook that interrupts any tool call with validate_only=false and asks him first. He ran dry runs for a label and a callout, committed only the label, read it back with a GAQL query, removed it, and confirmed the REMOVED status. His checklist: turn writes off in tools_config.yaml for reporting-only use, update allow-lists to the new prefixed tool names, lock which customer IDs the agent may touch, and pin a release tag. For budgets, target CPA and status changes he uses his own script with the same pattern: dry run, explicit confirmation, read back, change log.

Claude CodeGoogle Ads MCPGoogle Ads API

AdShift lists real agent workflows people have shared publicly. We summarize them and link to the original; check the source before you copy a setup.

More Google ads use cases All →

Latest Google changes All →

Monday brief

One new agent use case every Monday, alongside the platform changes that matter.