Bulk edit Amazon campaigns with AI, with guardrails on every change

What guardrails should an AI have before it bulk edits Amazon campaigns?

It should have five: a separate permission for edits, a preview of old and new values, your explicit confirmation, a hard line around irreversible actions, and a way to check the result afterward. Bulk is the dangerous word. One loose sentence in a chat can touch many campaigns at once.

Xnurta MCP connects Claude, ChatGPT and other MCP clients to your Xnurta data, and its ad-entity editing answers each of those five. Here is the short version, with the detail in the sections below.

What can you edit in bulk?

You can change campaign state, budget, bidding strategy, products, negatives, placement and audience bid adjustments, and keyword and product targets with their state and bid. Xnurta describes these edits as bulk operations, so one request can cover many campaigns, keywords or targets.

Creating new Sponsored Products campaigns is a different kind of write with its own scope. Create an Amazon campaign from a launch brief covers it.

What does the preview show, and when do you see it?

The preview shows which objects will change and from which value to which value, and it appears before any edit that involves money, bids or archiving. Say you ask for a 10% budget raise on three campaigns. You get three rows back, each with the campaign, its current daily budget and the new one. Nothing has been submitted yet.

Read the rows. Count them: three campaigns asked, three rows shown. If a number looks off, tell the assistant what to fix and ask for the preview again.

Other writes, such as adding negatives or changing a campaign's state, deserve the same habit. Ask the assistant to list the objects and the exact values it plans to change, and confirm before it executes. You can build that sentence into every prompt, as the examples below do.

How do you run a bulk edit, step by step?

You name the account, the objects and the exact change, ask for a preview, check it, then confirm. Six steps:

1. Check that write access is on and your connection carries the ad-entity editing scope (see the access rule below).
2. Name the ad account. The assistant sees only ad accounts your Xnurta login can access, main accounts and sub-accounts included.
3. Say which campaigns, keywords or targets to change, by name, ID or a rule such as "spent money, zero orders in 30 days."
4. Say the exact change: the value, the percentage or the state.
5. Ask for the preview and read it. Correct anything wrong.
6. Confirm. Then read the settings back.

In ad account [account name], which campaigns hit their daily budget cap in the last [7] days? Raise each one's daily budget by [10]%. Show me a preview with the campaign, the current budget and the new budget, and do not submit until I confirm.

In ad account [account name], list the campaigns that spent money with zero orders in the last [30] days. Pause them, not archive them. Show me each campaign's current state in a preview and wait for my confirmation.

In ad group [ad group name] of campaign [campaign name], lower the bids by [15]% on keywords with ACOS above [X]%. Show each keyword, its current bid and its new bid, and wait for my confirmation before you submit.

These prompts need write access. Reading numbers to choose what to change does not. The first prompt shows the pattern worth copying: a read question first, then an edit that builds on its answer.

How do you check what changed afterward?

You ask the assistant to read the settings back and compare them with the preview you confirmed. Xnurta's entity settings cover campaign status, bidding strategy and daily budget, keyword bids and status, and placement bid adjustments, and querying them is read only.

For the campaigns we just edited in ad account [account name], read back the current daily budget and state. Compare them with the preview I confirmed and flag any difference.

Keep the chat open or saved. The preview in it is your record of the old values. For a wider look at who did what in an account, by operator, action type and time window, see Who changed my Amazon campaign?.

Why pause a campaign instead of archiving it?

Because archiving cannot be undone, and pausing can. Xnurta gives you enable, pause and archive as states, and there is no way to delete a campaign afterwards. Archive a campaign and it stays archived.

So say the state you want, in plain words. If spend should stop for a week, say "pause." If you really mean archive, expect the preview to say so and be sure before you confirm. The same goes for products, which can also be enabled, paused or archived.

Who can run bulk edits on your account?

Only accounts with write access turned on, and only through a connection that carries the ad-entity editing scope. Reading never needs it.

Writing comes in three kinds: managed group management, ad-entity editing and Sponsored Products campaign creation. Each has its own permission scope. If you use a token, open MCP & Skill in Xnurta, click New token and choose the scope that covers editing ads.

Once your CSM switches access on, refresh your connection. Remove the Xnurta connector and add it again, or create a new token, because signing in again on the old connector keeps the old permissions. Then install the Xnurta skills in a new chat, since adding a connector never installs them. Amazon SA Ads Edit Tool is one of the official skills. Setup steps are in Connect Claude or ChatGPT to Xnurta MCP, and Read-only vs read-write MCP for Amazon advertisers helps you decide which access to start with.