How to Use SellerSheet MCP to Manage Amazon Ads Budgets

IntroductionCopy Anchor Link

Two budget problems eat more PPC revenue than any bad keyword. Campaigns run out of budget at lunchtime and sit dark all afternoon — and you only find out the next day. And shopping events arrive with no budget headroom because someone forgot to raise the caps the night before.

Amazon's Ads API has an answer for both: the Budget Usage API for live intraday consumption, and Budget Rules — automatic, self-reverting daily-budget increases driven by a schedule, a shopping event, or a performance metric. SellerSheet exposes this whole family as MCP tools, so your AI agent (Claude, ChatGPT, or any MCP client) can run the entire workflow for you, with your Google Sheet as the audit trail:

• ads_campaigns_budget_usage / ads_portfolio_budget_usage — live budget consumption for SP / SB / SD campaigns and portfolios.
• ads_create_budget_rules_for_campaigns / ads_update_budget_rules_for_campaigns / ads_create_associated_budget_rules_for_campaigns — create, update (also pauses, via ruleState: PAUSED), and associate schedule- or performance-based rules (SP / SB / SD).
• ads_get_budget_rules_recommendation — Amazon's upcoming shopping events with suggested increase percentages (SP / SB).
• ads_sp_get_budget_recommendations / ads_sb_get_budget_recommendations / ads_get_sd_budget_recommendations — suggested budgets plus missed-impression/click/sales estimates.
• ads_get_budget_recommendation — a starting daily budget for a campaign you haven't created yet.

Everything in this guide follows Amazon's official budget-rules documentation and has been verified end-to-end against the live Amazon Ads API across all three ad products, then put through a dedicated hardening pass so that a request the AI gets wrong is refused outright rather than half-applied. Where Amazon limits a capability to certain products or marketplaces, we say so.

PrerequisitesCopy Anchor Link

• A SellerSheet account with your Amazon store connected and Advertising authorized — both under Settings → Stores & Marketplaces in the SellerSheet app. The Ads consent is separate from Seller Central.
• An MCP client connected — follow How to Connect SellerSheet MCP (Claude, ChatGPT, Cursor, and others).
• Ads write access on the store for the API key your AI uses — reading usage and recommendations only needs read access, but creating or changing rules needs write. The store owner grants this per key under Settings → API & MCP.

Workflow 1 — The morning budget checkCopy Anchor Link

Your best campaign burned its whole budget by 1 PM and served nothing all afternoon. Yesterday's reports won't show it — they aggregate by day. By the time you notice in Seller Central, you've lost another afternoon of traffic.

ads_campaigns_budget_usage / ads_portfolio_budget_usage return live intraday consumption — the one number daily reports can't give you. Ask your AI:

The agent queries your campaigns, calls the usage endpoint, and writes a table into your sheet: campaign, budget, percent consumed, and the timestamp Amazon last evaluated usage. Campaigns near 100% are your action list — either a manual raise or, better, a budget rule (Workflows 2–3) so it never happens again.

What the usage data meansCopy Anchor Link

• budgetUsagePercent: spend as a percentage of the currently available budget (87.5 = 87.5% consumed).
• usageUpdatedTimestamp: when Amazon last evaluated usage — the figure is fresh but not second-by-second.
• Coverage: SP, SB, and SD campaigns, plus portfolios — up to 100 IDs per call (the agent chunks larger sets automatically).
• Portfolios: only portfolios with a budget cap report a meaningful percentage.

Workflow 2 — Schedule rules for Prime Day and peak daysCopy Anchor Link

Prime Day traffic tripled — and your campaigns went dark by 10 AM because the budgets were set for a normal Tuesday. Or you did remember to raise them, and then forgot to set them back, quietly overspending for a week.

A schedule-based budget rule (ruleType: SCHEDULE) raises the daily budget by a percentage you choose, for a window you choose, and reverts automatically when the window ends. Three flavors, straight from Amazon's schedule-based rules guide:

• Custom date range — "December 1–15, +50%". Works on SP, SB, and SD.
• Recommended shopping event — Amazon lists upcoming events (Prime Day, Black Friday…) per campaign with a suggested increase percentage; the rule binds to the event, so if Amazon shifts the dates, the rule follows. Events are offered for SP and SB campaigns.
• Recurring days — "every Friday–Sunday, +20%" (weekly recurrence on SB and SD; Sponsored Products rules run on daily recurrence). Amazon also supports intraday time windows on schedule rules in the US, CA, UK, IN, and JP marketplaces.

Behind that prompt the agent runs the exact three-step sequence Amazon's guide describes: fetch event recommendations (ads_get_budget_rules_recommendation returns each event's ID, dates, and suggested increase), create the rule with ads_create_budget_rules_for_campaigns using the event ID, then associate the rule to each campaign with ads_create_associated_budget_rules_for_campaigns. One rule can serve many campaigns, and each step's result lands in your sheet.

Workflow 3 — Performance rules: let the data raise the budgetCopy Anchor Link

A campaign is converting beautifully — ACOS 15%, well under target — and it's budget-capped. Every day you don't raise the budget is profitable traffic handed to a competitor. But you can't watch every campaign's metrics every day.

A performance-based rule (ruleType: PERFORMANCE) raises the budget only while a metric beats your threshold: "while ACOS < 20%, budget +25%". Amazon evaluates the metric over the trailing 7 days for sellers (14 for vendors). If the condition stops holding, the increase stops — the decision to spend more stays tied to the data.

Available metrics differ by ad productCopy Anchor Link

• Sponsored Products / Display: ACOS, CTR, CVR, ROAS.
• Sponsored Brands: top-of-search impression share (IS), new-to-brand % (NTB), and ROAS — not ACOS/CTR/CVR. (IS is unavailable for campaigns with video creatives.)
• Operators: greater/less than (or equal); EQUAL_TO exists on Sponsored Products only.
• Minimum budget: Amazon requires a minimum daily budget for performance rules to activate, so there's enough traffic to compute the metrics.

Workflow 4 — Right-size budgets with Amazon's own numbersCopy Anchor Link

"Is my daily budget enough?" For a new campaign you're guessing; for a running one you can't see the sales you didn't get because the budget ran out. Both answers exist — Amazon computes them — but they're buried in the API.

Two kinds of read-only tool surface Amazon's estimates:

• Running campaigns — ads_sp_get_budget_recommendations / ads_sb_get_budget_recommendations / ads_get_sd_budget_recommendations return a suggested daily budget per campaign plus the missed impressions, clicks, and sales Amazon estimates you're forfeiting at the current budget (up to 100 campaigns per call).
• New campaigns — ads_get_budget_recommendation takes your ASINs, targeting type, and bids before the campaign exists and returns a starting daily budget that shouldn't throttle delivery in week one. Sponsored Products only.

Workflow 5 — Verify what your rules actually didCopy Anchor Link

You set the rules and… then what? Automation you can't audit is automation you'll eventually turn off. You need to see which rules fired, what budget was actually in force, and whether the extra budget converted.

Amazon evaluates budget rules at the start of each day in the marketplace's own timezone (and re-evaluates immediately whenever a rule or the campaign's budget changes) — so "today" means the ad profile's day, not yours. Each rule carries a status you can read back: Active, On Hold (condition not currently met), Paused, Budget threshold not met, Pending Start, or Expired. Three ways to audit, in order of immediacy:

• List the rules on a campaign — ads_list_associated_budget_rules_for_campaigns shows every associated rule with its status. This is Amazon's own recommended source of truth: because rules stack, the single "applicable rule" field elsewhere can be incomplete.
• Watch usage during the window — re-run Workflow 1 while a rule is active to confirm the raised budget is being consumed (i.e., the increase is buying real traffic).
• Pull the audit columns in a report — for Sponsored Products, the campaigns report (ads_create_async_report, report type spCampaigns grouped by campaign) includes campaignRuleBasedBudgetAmount, campaignApplicableBudgetRuleId, and campaignApplicableBudgetRuleName — the rule-based budget that was in force, day by day, next to spend and sales.

Which workflow do you need?Copy Anchor Link

Good to know before you automateCopy Anchor Link

• Rules only ever increase, by percent, inside their window. Your base budget is never permanently modified; outside the window everything is exactly as you set it.
• There is no delete. Amazon's API has no rule-delete operation — pause a rule or disassociate it from the campaign; both stop it cold.
• Review before write. A well-prompted agent writes the rule plan to your sheet and waits for your confirmation before creating anything — the prompts in this guide ask for exactly that.
• Rules are attached one campaign at a time. Amazon's bulk-association shortcut isn't available to third-party tools (we tested it across three ad accounts and marketplaces), so the agent associates each campaign individually — same end result, nothing for you to do differently.
• New rules start as Pending Start — and stay there a while. A rule created for a future window shows Pending Start until its window opens, and in our live testing it took a few hours past marketplace midnight to flip to Active. That's expected. Don't re-create a rule that hasn't turned Active yet on event morning — you'd end up with two, and their increases stack.
• A wrong request fails cleanly, not halfway. If the AI sends a malformed budget request, it comes back rejected with the exact field and the allowed values — so the agent corrects itself and retries, instead of leaving a half-applied change on your account.

FAQCopy Anchor Link

What are Amazon Ads budget rules?Copy Anchor Link

Budget rules automatically increase a campaign's daily budget by a percentage you choose — either on a schedule (a date range or an Amazon shopping event like Prime Day) or when a performance metric such as ACOS or ROAS beats a threshold. When the window or condition ends, the budget reverts to normal on its own. They are supported for Sponsored Products, Sponsored Brands, and Sponsored Display.

Can budget rules lower my budget?Copy Anchor Link

No. Budget rules only increase the daily budget, by a percentage, inside the window you define. Outside the window your original budget applies unchanged — nothing is permanently modified.

Which metrics can performance-based rules use?Copy Anchor Link

Sponsored Products and Sponsored Display support ACOS, CTR, CVR, and ROAS. Sponsored Brands uses a different set: top-of-search impression share (IS), new-to-brand percentage (NTB), and ROAS. Metrics are computed over the previous 7 days for sellers (14 for vendors).

What happens if several rules apply to one campaign at once?Copy Anchor Link

Every rule whose condition is met applies, and their percentage increases are added together on top of the daily budget. A campaign can carry up to 250 rules, so it's worth listing a campaign's rules before adding another.

How do I delete a budget rule?Copy Anchor Link

Amazon's API has no delete operation for budget rules. Instead, pause the rule (set its state to PAUSED) or disassociate it from the campaign — either one stops it from affecting budgets.

Do I need special permissions to manage budget rules with AI?Copy Anchor Link

Viewing budget usage, rules, and recommendations needs read access to the store's Ads data. Creating, updating, associating, or pausing rules requires Ads write access, which the store owner grants per API key under Settings → API & MCP in the SellerSheet app.

What happens if the AI sends a bad budget request?Copy Anchor Link

It is refused before anything changes on your account, with a message naming the exact field that was wrong and the values Amazon accepts. The agent reads that, corrects the request, and retries — so a mistake costs a round trip, not a half-applied budget change you have to unpick.