Amazon Seller MCP Server — AgentXray

Amazon suggested bid range

get_amazon_bid_recommendations

Read-onlyIdempotent

AMAZON's own suggested bid range for the live keywords in one ad group - what the auction currently costs. A DIFFERENT number from the seller's break-even CPC, which is priced against their measured margin. Report both, say which is which, never average them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ad_group_id": "<ad_group_id>"
    },
    "name": "get_amazon_bid_recommendations"
  }
}

Input Schema

Name	Required	Description	Default
`ad_group_id`	Yes	Amazon ad group id (from get_ads_targets). This alone identifies the account and marketplace — do not pass one separately.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the value is Amazon's live-auction cost estimate and must not be conflated or averaged with break-even CPC. It does not cover return format or any account/marketplace scoping beyond what the schema states.

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?

Two tight sentences, front-loaded with the core meaning of the metric and followed by an actionable reporting constraint. Every clause earns its place; nothing is redundant.

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-parameter read-only tool with no output schema, the description supplies the semantic framing an agent needs to interpret and report the result correctly. The main remaining gap is that it doesn't describe the shape of the returned range (low/high bounds) or failure behavior when no live keywords exist.

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 single ad_group_id parameter is fully documented in the schema, including that it alone identifies account and marketplace. The description adds no parameter-level detail, 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 states a specific verb+resource (Amazon's suggested bid range for live keywords in one ad group) and clarifies what the number represents ('what the auction currently costs'). It sharply distinguishes this metric from the seller's break-even CPC, but names no sibling tool, so the 5-level sibling differentiation is not fully met.

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?

It gives a clear directive about how to report the value ('report both, say which is which, never average them'), which is genuine usage guidance for handling the result. However, it never says when to reach for this tool versus alternatives like get_ads_targets or profit-based tools; usage is only implied.

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?