Skip to main content
Glama

Amazon Seller MCP Server — AgentXray

Wasted, winning and harvestable search terms

get_ads_search_term_verdicts
Read-onlyIdempotent

Search terms judged over every term: wasted (twice the account's clicks-per-order and no order), best sellers against the measured break-even, and harvest candidates not yet an exact keyword. Read its narrative as the answer.

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

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in store days, 1-90 (default 30).
limitNoMax terms per list (default 10, max 25).
marketplace_idNoMarketplace (inferred when only one is connected).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety bar is low. The description goes further by disclosing the analytical thresholds (twice the account's clicks-per-order with no order; break-even for best sellers) and by telling the agent that the `narrative` field carries the actual answer — real behavioral context beyond the annotations. It stops short of describing pagination or the shape of the three lists.

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 with no filler; the classification criteria are front-loaded and the output instruction closes it out. The first sentence is dense with nested parentheticals, which slightly slows parsing, but nothing is wasted.

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

Completeness3/5

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

There is no output schema, so the description must carry return-value meaning. It only gestures at the response via 'narrative' and the general notion of 'lists'; it never states whether three lists are returned, how verdicts are keyed, or how the narrative relates to the structured lists. Adequate but incomplete for a computed-report tool.

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 `days`, `limit` and `marketplace_id` are fully documented in the schema with defaults and ranges. The description adds no parameter-level detail (e.g., whether `days`/`limit` apply uniformly to all three verdict lists), so the baseline 3 is correct.

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 a specific output: search terms classified into three verdict buckets (wasted, best sellers, harvest candidates), each with a stated criterion. This is clearly distinguishable from the raw-data sibling get_ads_search_terms, even though that sibling is never named. The verb is implied ('judged') rather than stated, which keeps it 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 Guidelines3/5

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

Usage is implied — this is the judged/verdict view of search terms rather than the raw list — but there is no explicit when-to-use, when-not, or named alternative against get_ads_search_terms / get_brand_search_terms. 'Read its `narrative` as the answer' tells the agent how to consume the output but not when to reach for this tool.

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