What campaign creation looks like with Claude
In the standard workflow, campaign creation requires moving between the keyword planner, the campaign setup wizard, the ad copy editor, and the billing settings. Each step is independent and context does not carry between them.
With MCP Ads, Claude can pull keyword ideas, suggest a campaign structure, write RSA headlines and descriptions, and create the campaign — all in one conversation thread. The context from step one is still available at step five.
Keyword strategy and match types
Start by asking Claude to research keywords for your product or service. It can pull search volume, competition, and CPC estimates through the Google Ads API, and suggest which keywords belong in which ad groups based on theme.
Match type decisions are usually the first thing new advertisers get wrong. Claude can explain the tradeoffs and recommend a starting mix based on budget and account maturity.
- Find keywords for [product] with monthly volume over 500 and low competition
- Group these keywords into ad groups by intent
- Recommend match types for a new campaign with a $30/day budget
- Add negatives for any irrelevant terms in this keyword list
Writing Responsive Search Ads
RSAs require 15 headlines and 4 descriptions. Writing variations that are meaningfully different, avoid repetition, and hit the character limits is tedious to do manually. Claude can generate a full RSA asset set from a product description, a URL, or a list of selling points.
The best RSA sets mix benefit-led headlines, feature-specific headlines, and CTAs. Ask Claude to label each asset by type and explain the logic — that makes it easier to review and approve.
- Write 15 RSA headlines for [product]: include benefits, features, and CTAs
- Generate 4 RSA descriptions under 90 characters each
- Check this RSA for asset strength and suggest improvements
- Rewrite the weak assets to improve predicted CTR
Budget, bidding, and geo targeting
Once the ad structure is ready, Claude can set the daily budget, choose the bid strategy, and configure geo targeting. For new campaigns, Maximize Clicks is usually the right starting strategy — it builds impression share before switching to tCPA once conversion data exists.
Geo targeting decisions depend on where your product is available and where your strongest conversion rates are. Claude can pull performance data from existing campaigns to inform the geo strategy for the new one.
From draft to live
MCP Ads creates campaigns in PAUSED status by default. That gives you time to review everything before enabling. Ask Claude to summarize the campaign configuration — budget, keywords, ad groups, match types, bid strategy — before you approve.
Once enabled, the same connection lets you monitor performance, add negatives, and adjust bids from the same workflow without switching tools — see how to connect Google Ads to Claude for the ongoing reporting side of that workflow.
Doing this with Claude connected to the account
The sections above describe the workflow in general terms. This is what it looks like as actual prompts, with the tool each one calls, once Google Ads is connected through MCP Ads.
Prompt 1: "I sell ergonomic office chairs in the UK. Give me 30 keyword ideas with volume and top-of-page bid, split into three ad groups by theme, and tell me which existing campaigns already cover any of them." Claude calls google_ads_keyword_ideas for the planner data and google_ads_keyword_performance to check for overlap with what is already running. What comes back is a proposed structure rather than a flat list: three ad groups, each with ten keywords, suggested match types, and a note on the four keywords already live in another campaign. As an illustrative example, the planner might show "ergonomic office chair" at 12,000 monthly searches and a £1.40 top-of-page bid, which sets the budget conversation before anything is built.
Prompt 2: "Build the campaign: Search only, £40 a day, Maximize Clicks with a £2 cap, UK targeting, and one RSA per ad group with 12 headlines and 4 descriptions using the themes we discussed. Add sitelinks for Delivery, Warranty, and Showroom." Claude runs the sequence: google_ads_create_budget, google_ads_create_campaign, google_ads_add_location_target, google_ads_create_adgroup for each group, google_ads_bulk_create_keywords, google_ads_create_responsive_search_ad, and google_ads_create_sitelink_asset. Every step is a write, so before the first call Claude shows you the full plan — budget, bid strategy, geo, ad groups, keywords, headlines — and waits for a yes. The campaign is created paused.
Prompt 3: "Summarize what you built, check each RSA for ad strength issues, and then enable it." Claude reads back the campaign from google_ads_list_adgroup_keywords and google_ads_list_ads_in_adgroup so you are reviewing what is actually in the account, not what was intended. google_ads_enable_campaign is the last write, and it is the one that starts spend, so it is confirmed separately.
If you do this often, the pre-launch checklist in the skills library runs the review step automatically before enabling.
Where the manual way still wins
The Google Ads editor shows an ad preview rendered the way it will appear on the results page; the API does not return one, so Claude cannot show you how the headline combinations will look together on mobile. Ad strength is also only available after the ad exists, not before. Check the preview in the UI once before enabling.
The offer and the landing page are still yours. Claude can write twelve headlines that use the keyword; it cannot know that free delivery ends next week or that the showroom is closed on Mondays. Read every headline before approving, because once the campaign is enabled those words are what customers see.
