PPC & Ads · from a Reddit thread, Oct 17, 2026 · Added
Overnight Bid Fixes Across 3,000 Campaigns with Claude and an Owned Data MCP
Sync all Amazon Ads and Seller Central data into your own database and let Claude propose and run approved changes
“each saving $15k to $20k a year”
Per source Reported by an agency about its own client work, not independently verified.
Copy-paste prompt
Using my connected Amazon data, run this morning check for [brand]: 1. Campaigns whose budget ran out before [6 PM] yesterday. 2. Campaigns with ACOS above [X]% yesterday compared with their 14-day average. 3. Campaigns with zero impressions. 4. Listings suppressed since yesterday. 5. ASINs with under 14 days of cover that still have ads running. 6. Every bid, budget or status change made yesterday and who made it. Write a plain-English plan of fixes and wait for my approval before changing anything.
The source didn't publish its exact prompt. We wrote this starter so you can try the same workflow. Replace anything in [brackets].
See the original Reddit thread
What they did
A former seller (about $3M a year at the peak) who now runs an Amazon agency built two pieces. One syncs, daily per profile, Ads data (SP, SB and SD campaigns, targeting, search terms, placements), Seller Central data (sales and traffic, orders, settlements, returns, listings, Search Query Performance, inventory), the Ads change history, the hourly marketing stream, weekly AMC queries and Keepa data into a database per brand. The other is an MCP server in front of that database that Claude (claude.ai, Claude Desktop or Claude Code) talks to, all in his own Cloudflare account. Every morning Claude checks each account for budgets that ran out early, ACOS spikes, zero-impression campaigns, listings suppressed overnight, ASINs under two weeks of cover and everything that changed yesterday. Every action produces a plan in plain English, and nothing moves without approval unless a rule is set to run on its own.
How it went
During a sale event one brand had 3000+ campaigns live and bids were creeping up overnight. Claude checked the hourly data, worked out which bids to pull back and which budgets to protect, built the bulk action and asked for approval; he approved on his phone and it ran against the Ads API. He says that would normally need 3 people monitoring. The setup costs about $10 a month in hosting, and he says three friends' brands using it are each saving $15k to $20k a year.
We only report what the source says. Results are self-reported unless noted.
Worth knowing
Agency-reported, and he offers a one-click template of the setup, so he has something to sell. His Amazon notes are useful on their own: reports are async, retention is 60 to 95 days so backfill on first connect, re-pull a trailing window every day because attribution keeps changing, and direct Ads API access can take weeks.