Amazon Seller MCP Server — AgentXray

Negative keywords on the account

get_ads_negatives

Read-onlyIdempotent

Every negative keyword on the account, with its campaign and ad group and a self_block flag. self_block means the seller also bids on that exact term in the same ad group — the campaign blocks a keyword it pays for. A negative is invisible by construction, so this list is the only way to see one.

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_negatives"
  }
}

Input Schema

Name	Required	Description	Default
`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.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnly and non-destructive, so the bar is lower, yet the description adds real behavioral insight: it defines the non-obvious self_block flag and explains why negatives are invisible elsewhere. It doesn't discuss pagination or response shape, but that's secondary for a read-only list.

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

Conciseness5/5

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

Three tight sentences. The key concept (self_block) is defined immediately, and the rationale for the tool's existence is front-loaded without waste.

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

Completeness4/5

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

For a single read-only parameterless list with no output schema, the description covers the payload, the special flag, and the motivation. A note on output format or pagination would close the gap, but nothing essential to calling it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the schema already carries a rich marketplace_id description, so the description doesn't need to repeat it. It adds only the scope note implied by 'Every negative keyword on the account,' leaving the schema to do the heavy lifting, which is appropriate.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Every negative keyword on the account,' and immediately explains the payload (campaign, ad group, self_block flag). It is unmistakably distinct from siblings like get_ads_targets or get_ads_search_terms.

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

Usage Guidelines3/5

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

The closing line, 'this list is the only way to see one,' implies when to use it – when you need visibility into negatives – but no explicit alternative or exclusion is named. Usage is inferable rather than stated.

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

All Amazon Seller MCP Server — AgentXray 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?