-
This is right up my alley. We’ve been running Claude connected to Google Ads and Meta Ads through MCPs for about a year.
Biggest thing I’d warn you about: do not let it do math. It will confidently give you wrong ROAS, wrong CPA, wrong everything. It predicts text, it doesn’t calculate. We had it invent a ROAS out of thin air. If you need actual metrics, have Code build you Python scripts and let Claude call those instead.
Also heads up, Google Ads API reports costs in micros (1,000,000 = $1). Claude won’t know that unless you tell it. It’ll happily compare micro costs to dollar costs without flinching.
What actually made it useful for us: stop asking it to ‘analyze my account.’ Way too broad. Give it very specific tasks. ‘Review these search terms and flag anything with spend over $50 and zero conversions.’ Specific in, specific out.
Your compliance skill is the right idea. Narrow scope, one job, clear output. Build more of those. Search term categorization, negative keyword flagging, ad copy review by match type. The more specific each skill is, the better the output gets.
The real unlock for us was separating the thinking from the calculating. Claude interprets and analyzes. Code does the math. That combo is where it gets actually reliable.
