Skip to main content
Glama
Sign In

SEO and Keyword Data API

by com.duoleads.keywords
OverviewDiscussionsAdmin

Amazon search results (products)

amazon_search
Read-onlyIdempotent

Amazon search results for a query: up to 100 products of the results page with position, ASIN, title, product link, sponsored flag, price, currency, rating and rating count, bought-past-month, Amazon's Choice and Best Seller badges, plus related searches, 18 Amazon stores (default US), from Amazon, $0.012 a call. Use when checking what ranks on Amazon for a search. No results is an empty answer, which is still charged. Bad input is a free 400; a data source failure is not charged. Price: $0.012 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "q": "<q>"
    },
    "name": "amazon_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesThe search (at most 200 characters).
limitNoRows to return, 1-100. Default 20.
locationCodeNoAmazon store by location code: 2036, 2076, 2124, 2250, 2276, 2356, 2380, 2392, 2484, 2528, 2616, 2682, 2724, 2752, 2784, 2792, 2826, 2840 (2840 = amazon.com, 2826 = amazon.co.uk, 2276 = amazon.de...). Default 2840.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), yet the description goes well beyond them: cost of $0.012 per successful call, that an empty result set is still charged, that a 400 is free, that a data-source failure is not charged, and that payment is passed via _meta['x402/payment'] in USDC on Base. This billing and failure semantics are exactly the behavior an agent cannot infer from structured fields.

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?

Information-dense and front-loaded: purpose, payload fields, when-to-use, then cost/error semantics. The only waste is the price stated twice ('$0.012 a call' early and again in the closing 'Price:' sentence), which could be consolidated into one place.

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

Completeness5/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 compensates by listing the fields returned per product plus related searches and store coverage. Combined with the upfront pricing and the distinction between charged and uncharged outcomes, an agent has everything needed to decide and call correctly.

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 q, limit and locationCode are already documented, including the location-code examples. The description adds only light framing ('up to 100 products', '18 Amazon stores (default US)') and offers no extra detail on how limit interacts with paging or which codes map to which marketplace beyond the schema. Baseline 3 applies.

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 ('Amazon search results for a query') and immediately enumerates the returned fields (position, ASIN, title, sponsored flag, price, rating, badges, related searches). Against siblings like bing_search, google_search and youtube_search, the Amazon scope is unmistakable without opening any schema.

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?

'Use when checking what ranks on Amazon for a search' gives an explicit use case, and the store-coverage note implies the regional scope. It does not name an alternative or state when NOT to use it, so routing is clear but not fully disambiguated.

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

All SEO and Keyword Data API toolsInspect
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