Google Ads
Create paused Google Ads Search campaigns, research keywords and report on performance, under 3 house rules.
Google Ads support covers Search campaigns only, creation first. It runs from the CLI under adwarp google and from the local MCP server as the gads_* tools. The hosted endpoint does not register the Google tools (see Hosted endpoint).
adwarp google auth login
adwarp google accounts list # proves the token and OAuth client work
adwarp google keywords "revops automation" --url https://example.com/product
adwarp google conversions list
adwarp google launch --brief examples/google-brief.json # dry run
adwarp google launch --brief examples/google-brief.json --apply # create it, paused
adwarp google campaigns list
adwarp google report perf keyword -p last_30_daysA launch creates the budget, campaign, geo and language targeting, ad groups, keywords, and responsive search ads in a single atomic mutate. It either lands whole or not at all, so a failure cannot leave half a campaign behind. Every write is validated server-side first, which makes the dry run a genuine check by Google rather than a local guess.
To connect your account first, see Set up Google Ads.
House rules
Adwarp hard-codes 3 house rules, because all 3 default the wrong way in the Google Ads UI and quietly waste B2B budget:
- Search network only. Display expansion and search partners are off.
- Physical presence only. "US" means people in the US, not people anywhere who searched about it.
- Manual CPC to start. Smart bidding with no conversion history spends unpredictably. Switch in the UI once there is data.
Google has no draft status, so campaigns, ad groups, and ads are created paused, and no create schema can express any other status. Google campaigns can only be switched on in the Google Ads UI.