Skip to main content
Glama

Amazon Seller MCP Server — AgentXray

Amazon weekly search-term ranking

get_brand_search_terms
Read-onlyIdempotent

Amazon's own weekly Brand Analytics search-term ranking for one marketplace on the connected seller account: which customer search terms rank where, the ASINs shoppers clicked on each, and how each term moved against the previous week. Rank 1 is the most-searched term, so a smaller rank is better. Requires Brand Registry; an unenrolled seller gets a named refusal rather than an estimate. Requires a marketplace id from list_my_marketplaces.

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": {
      "marketplace_id": "<marketplace_id>"
    },
    "name": "get_brand_search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 50).
accountNoSeller id of the client account (from list_my_accounts). Only needed with several accounts.
search_termNoOptional: only terms containing this text.
marketplace_idYesRequired marketplace id (from list_my_marketplaces).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description adds real value beyond them by disclosing the auth requirement (Brand Registry) and the failure behavior for unenrolled sellers (named refusal rather than an estimate). It also clarifies the rank semantics (rank 1 is best).

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?

Front-loaded with what the tool returns, then rank semantics, then the two prerequisites. Four dense sentences, each carrying information; slightly long but nothing is filler.

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?

With no output schema, the description carries the burden of describing the return, and it does so (ranks, clicked ASINs, week-over-week movement). Safety is covered by annotations and prerequisites are stated, leaving only minor gaps like pagination/return size.

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%, so every parameter is already documented in the schema. The description reinforces marketplace scope and the account context but adds no syntax or format detail beyond what the schema provides, so 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?

States a specific verb+resource: Amazon's weekly Brand Analytics search-term ranking for one marketplace, and enumerates the content (ranks, ASINs clicked, week-over-week movement). Clear enough to separate from the ads-oriented sibling get_ads_search_terms, though it never names the alternative explicitly for the ads-vs-organic distinction.

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?

Gives concrete prerequisites: requires Brand Registry, requires a marketplace id from list_my_marketplaces, and one marketplace per call. It does not explicitly state when to prefer this over get_ads_search_terms, so the when-not side is by inference rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources