Amazon Seller Central & Ads MCP

Ad campaigns with ids and budgets

get_ads_campaigns

Read-onlyIdempotent

Campaigns on the connected Amazon Ads account WITH their Amazon campaign ids, state, daily budget, measured spend and sales, and budget utilisation. Call this before proposing a budget or a pause: both need the campaign id, and utilisation is what a budget decision turns on — a campaign running at 40% of its budget is not budget-constrained, so raising it buys nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ads_campaigns"
  }
}

Input Schema

Name	Required	Description
`days`	No	Window in days (default 30, max 90).
`state`	No	Which campaigns to list (default enabled: paused and archived campaigns spend nothing). counts_by_state always counts every state regardless.
`marketplace_id`	No	Optional. Scope to ONE marketplace. Omit only when the seller has a single marketplace, or when they really do mean every market at once — figures from different marketplaces are in different currencies and are never converted. Call list_my_marketplaces first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

addedInput schema / properties / state

Added value: +{
+  "description": "Which campaigns to list (default enabled: paused and archived campaigns spend nothing). counts_by_state always counts every state regardless.",
+  "enum": [
+    "enabled",
+    "paused",
+    "archived",
+    "all"
+  ],
+  "type": "string"
+}

First observedSep 23, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this a safe, idempotent read (readOnlyHint, idempotentHint, destructiveHint=false), so the safety profile is covered. The description adds genuinely useful context beyond annotations: that it acts as a prerequisite for budget/pause proposals and how to interpret utilisation. It does not discuss pagination or result shape, so it is not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is returned, then the usage rationale. The second sentence is long and slightly discursive ('so raising it buys nothing'), but every clause carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a fully documented input schema, the description supplies exactly what is missing: what the tool returns and when to reach for it. An agent has enough to select and call it correctly, including the prerequisite ordering for budget proposals.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already documents days, state, and marketplace_id including the marketplace/currency caveat and the counts_by_state note. The description adds nothing about parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (campaigns on the connected Amazon Ads account) and enumerates the returned attributes: campaign id, state, daily budget, spend, sales, utilisation. That field list implicitly separates it from richer siblings like get_ads_overview, but no sibling is named outright, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger — 'Call this before proposing a budget or a pause' — and justifies it (the campaign id is required, utilisation drives the budget call). There is no when-not guidance or named alternative, but the context for use is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Amazon Seller Central & Ads MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?