Skip to main content
Back to Blog
Analytics
Updated Aug 19, 2026

11 AI Prompts Every Amazon Seller Should Run Weekly

Once your Amazon data is reachable through an MCP connection, the bottleneck moves from access to asking. These are the prompts that change what a seller does on a Monday, with the phrasing that keeps answers accurate.

M
·COO at Nova AnalyticsLinkedIn

Max leads operations at Nova Analytics, helping Amazon sellers optimize their business performance through data-driven insights and strategic automation.

Aug 19, 2026·9 min

TL;DR - Key Takeaways

  • The value of an AI assistant is not the prompt, it is whether live, reconciled data sits behind it.
  • Good prompts name a decision, a scope and a threshold. Vague prompts produce essays.
  • The five prompt families that pay off: profit movers, PPC waste, inventory risk, listing damage and weekly briefings.
  • Always ask for the number that drives the action, not the ranking on its own.
  • Ask the assistant to state what it could not check. That single line prevents most confident-but-wrong answers.

Once your Amazon data is reachable through an MCP connection, the bottleneck moves from access to asking. These are the prompts that actually change what a seller does on a Monday, grouped by the decision they serve, with a note on why each one is phrased the way it is.

Before the prompts: what makes one work

The Model Context Protocol lets an assistant discover the tools a server exposes and call them with typed arguments, as described in the protocol documentation. That means your prompt is really an instruction about which tool to call and with what filter. Three habits do most of the work:

  • Name the scope. Marketplace, date range, and whether you mean all SKUs or a segment.
  • Name a threshold. "Spent more than $100 with zero orders" beats "wasted spend".
  • Name the output shape. A ranked table with the deciding number in a column is far more usable than prose.

Profit and margin prompts

1. Find what actually moved

Compare last 30 days to the previous 30 days. Show the 10 SKUs with the biggest drop in net profit, with net sales, ad spend, units and contribution margin for both periods.

Ranking by profit change rather than sales change filters out the SKUs that only look busy. The paired columns let you see instantly whether the cause is volume, price or spend.

2. Ask why, on one SKU

For the worst SKU in that list, explain the movement: traffic, conversion rate, average price, buy box share, promotions, ad spend and rank, this period versus last.

This is the follow-up that stops the guesswork. A conversion drop with stable traffic is a listing or price problem; a traffic drop with stable conversion is a rank or ad problem.

3. Catch the money-losers

List every SKU with negative net profit over the last 60 days, sorted by total loss, with units sold and the largest fee category for each.

The fee column turns a list into a plan: oversize fulfilment, storage and returns each imply a different fix.

Add one line to every analysis prompt

Finish with: "State any figure you could not retrieve rather than estimating it." Assistants are far better at flagging a gap when you give them permission to. It converts silent hallucination into an explicit missing data point.

Advertising prompts

4. Negative keyword candidates

Show customer search terms from the last 30 days with more than $75 spend and zero orders, ranked by spend, with clicks and CPC.

This is the highest-return prompt in the list. The threshold and the zero-order filter run server side, so you get a short actionable table instead of thousands of rows.

5. Spend above break-even

Which campaigns had an ACoS above the break-even ACoS of the products they advertise last month? Show spend, sales, ACoS and contribution margin.

ACoS alone cannot answer this. It only works when the assistant can reach fee and COGS data alongside ad data.

6. Promote the winners

From auto campaigns in the last 60 days, show search terms with at least 3 orders and an ACoS below 20%, so I can promote them to exact match.

The discovery half of the same report. Most sellers run the waste query and forget this one.

Run these prompts on your own numbers

Nova MCP connects Claude, ChatGPT or Gemini to your live profit, PPC, inventory and listing data, read-only.

Try Nova for free

Inventory prompts

7. What runs out first

List SKUs with fewer than 30 projected days of inventory, sorted ascending, with sales velocity, available units and incoming units.

Projected days of cover, not raw units, is the reorder trigger. Incoming units in the same table stops you double-ordering.

8. Dead stock

Show FBA SKUs with stock on hand and no sales in the last 30 days, with units held and estimated monthly storage cost.

Pairing units with storage cost turns a cleanup task into a ranked one.

Listing health prompts

9. Silent revenue leaks

Which of my listings are currently suppressed, not buyable or search suppressed? Rank by trailing 90-day sales so I fix the expensive ones first.

Severity alone ranks by Amazon's view. Ranking by your sales ranks by yours.

10. Buy box loss

Show ASINs where I no longer own the buy box, with the current buy box owner, their price and my price.

The price gap column tells you immediately whether it is a hijacker problem or a pricing problem.

The Monday briefing prompt

The one prompt worth saving as a reusable instruction, because it replaces a dashboard tour:

11. Weekly business briefing

Give me a Monday briefing for last week versus the week before: net sales, net profit and margin by marketplace; the 3 biggest profit gainers and losers by SKU; any SKU with under 21 days of cover; any suppressed or non-buyable listing above $500 in trailing sales; and search terms over $50 spend with zero orders. Keep it under 400 words and end with the three actions you would take first.

It bundles five tool calls into one artefact and forces a prioritised recommendation at the end. The word limit matters, otherwise you get a report nobody reads.

For the connection itself, the Claude setup guide walks through it, and the Amazon MCP hub lists which tool each of these prompts resolves to. Anthropic's original protocol announcement is still the clearest explanation of why this works at all.

AI prompts for Amazon sellers: common questions

Getting reliable answers from an assistant connected to live data

No. Without a live connection the assistant either refuses or guesses from a pasted export, which is how wrong margin numbers end up in decisions. These prompts assume the assistant can call a seller-data MCP server that returns real figures.
Not usually. A good MCP server publishes a metric catalog the assistant reads before answering, so plain language like 'contribution margin' or 'days of cover' maps to the right field. Naming a specific marketplace or date range does help.
It should not, if the server computes the metric rather than the model. When numbers drift, the usual cause is the model doing arithmetic on raw rows. Ask for the underlying figures and check whether the server returned a computed metric or a data dump.
In most assistants you can save a prompt as a reusable project or custom instruction and run it on a cadence you control. A Monday morning briefing prompt is the single most-used pattern we see.
Claude, ChatGPT and Gemini all support remote MCP servers, and all three handle these prompts. Differences show up in long multi-step analysis rather than in whether the data arrives.

Ready to Transform Your Amazon Business?

Join thousands of successful sellers who use Nova Analytics to make data-driven decisions and maximize their profits.