Skip to main content
Glama

Amazon Product

amazon_product
Read-onlyIdempotent

Looks up Amazon products. With asin it returns one product (asin, title, brand, price, availability, rating, reviews_count, url, image); with query, up to 20 results from the first search page (title, url, asin, price, rating, reviews_count, position). Send asin or query, not both; marketplace selects the Amazon site (default com). It does not return reviews, offers, bestseller lists or price history, nor prices from other merchants (use google_shopping_prices). A search with no matches is charged; errors are not. Required: asin or query.

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": "amazon_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinNoAmazon product ID (ASIN), exactly 10 letters or digits, e.g. "B00CH9QWOU", for one product. Send asin or query, not both.
queryNoProduct search text, 1-500 characters, e.g. "espresso machine". Send query or asin, not both.
resultsNoMaximum search results returned for query, integer 1-20, default 10, e.g. 5. Not used with asin.
marketplaceNoAmazon site as its domain suffix, e.g. "com" for amazon.com, "co.uk" or "it". Omit for com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / asin / description
      Previous value: -"Ten-character Amazon product identifier for a product lookup."New value: +"Amazon product ID (ASIN), exactly 10 letters or digits, e.g. \"B00CH9QWOU\", for one product. Send asin or query, not both."
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon marketplace domain suffix, such as com or co.uk."New value: +"Amazon site as its domain suffix, e.g. \"com\" for amazon.com, \"co.uk\" or \"it\". Omit for com."
    • changedInput schema / properties / query / description
      Previous value: -"Product search query; do not combine with asin."New value: +"Product search text, 1-500 characters, e.g. \"espresso machine\". Send query or asin, not both."
    • changedInput schema / properties / results / description
      Previous value: -"Maximum number of Amazon search results to return."New value: +"Maximum search results returned for query, integer 1-20, default 10, e.g. 5. Not used with asin."
  2. Added
  3. Removed
  4. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses the return shape for each mode, the first-page/search cap, and a non-obvious billing behavior ('A search with no matches is charged; errors are not'). Those are exactly the behavioral facts an agent cannot infer from the annotations or schema.

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?

The description is compact and front-loaded: it states what the tool does, then mode behavior, then exclusions and cost notes. Every sentence carries unique, decision-relevant information.

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 appropriately lists the returned fields for both modes, explains defaults and mutual exclusivity, and covers cost and out-of-scope data. Nothing material for correct invocation appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds mode-level meaning by explaining what each of asin versus query produces. It also confirms marketplace defaults to 'com' and that the two request modes are mutually exclusive, though most of this is repeated from the schema.

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 ('Looks up Amazon products') and immediately distinguishes its two modes: a single-product lookup by ASIN versus a up-to-20-result search by query. It also names the exact sibling to use when prices from other merchants are wanted, making it easy to tell apart from google_shopping_prices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives explicit inclusion rules ('Send asin or query, not both') and explicit exclusion rules ('does not return reviews, offers, bestseller lists or price history, nor prices from other merchants'). The alternative tool is named for the out-of-scope case, so the routing decision is unambiguous.

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