Skip to main content
Glama
mansournorouzi

Amazon SP-API MCP Server

get_search_terms_report

Retrieve top search terms with frequency rank, click, and conversion share by ASIN to analyze customer search behavior.

Instructions

Get Brand Analytics search term report showing top search terms, search frequency rank, and click/conversion share by ASIN. Requires Brand Registry. Helps understand how customers find your products.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startDateYesStart date in YYYY-MM-DD format
endDateYesEnd date in YYYY-MM-DD format
Behavior3/5

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

No annotations provided, so the description must convey behavioral traits. It notes the Brand Registry requirement and the report nature, but lacks details on read-only status, response size, pagination, or refresh cadence. Adequate but not thorough.

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 concise sentences: first covers purpose and output fields, second adds prerequisite and value. No superfluous words, well front-loaded.

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?

Given a simple date-range tool with complete schema and no output schema, the description covers purpose, prerequisite, and use case. Minor gaps: no mention of timezone, data aggregation level, or date range limits, but sufficient for selection.

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 coverage is 100% with clear date parameter descriptions. The description adds no further clarification beyond the schema, so baseline score of 3 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?

Clearly states the tool retrieves a Brand Analytics search term report listing top search terms, frequency rank, and click/conversion share. Distinct from sibling tools like get_sales_traffic_report or get_catalog_item by focusing on search terms and requiring Brand Registry.

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?

Explicitly mentions the prerequisite (Brand Registry) and the use case (understanding customer search behavior). Does not provide alternatives or when-not-to-use guidance, but the context is clear given the sibling set.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mansournorouzi/amazon-sp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server