Skip to main content
Glama

Amazon MCP

Amazon product details by ASIN (PLN)

amazon_product

Full details of one Amazon product by ASIN (or product URL — its store is used unless marketplace says otherwise) via SerpAPI's amazon_product engine; one credit, ~10–25 s. Returns every offer with PLN prices — the main price, each purchase option (new/used/…), other sellers — and the cheapest new one, plus variants (each with its own ASIN), rating histogram, specifications, bullet points, category path and a few top reviews. The same ASIN can be looked up on another store (ASINs are mostly shared across EU stores). Result shape: { source, fetchedAt, query, marketplace, asin, title, brand?, url, categories?, images?, rating, reviews, rating_histogram?: { '5': pct, … }, reviews_summary?, bought_last_month?, price, price_text, currency, price_pln, max_price?, old_price?, discount_percent?, coupons?, promotions?, delivery?, stock?, purchase_options?: [{ type, price, currency, price_pln, stock?, delivery?, features? }], other_sellers?: [{ sold_by, ship_from, price, currency, price_pln, delivery?, seller_rating?, seller_reviews?, seller_feedback? }], cheapest_offer?: { source, seller?, price_pln }, variants?: [{ dimension, options: [{ asin, name, selected? }] }], about_item?, specifications?, details?, top_reviews?, fx, note? }.

Input Schema

NameRequiredDescriptionDefault
asinYesASIN (10 characters, e.g. 'B09Y2MYL5C', from an amazon_search result) or an Amazon product URL containing /dp/<ASIN>.
languageNoStore language as <language>_<REGION>, e.g. 'en_GB' for English titles on amazon.de. Default: the store's own (de_DE on amazon.de) — each store only offers a few (amazon_marketplaces lists them).
no_cacheNoForce a fresh SerpAPI fetch, bypassing this server's 5-minute result cache. Default false.
marketplaceNoAmazon store: its code (pl, de, fr, it, es, nl, be, se, uk, tr, us, ca, mx, br, au, jp, in, cn, sg, ae, sa, eg) or domain (amazon.de, amazon.co.uk…). Default pl. Overrides a URL's own store — to look the ASIN up elsewhere.
delivery_zipNoDelivery postal code within shipping_location's country (or the store's), e.g. '00-001'.
other_sellersNoInclude the other sellers' offers. Default true.
convert_to_plnNoAdd price_pln at the NBP mid rate. Default true.
include_reviewsNoInclude up to 3 top reviews (600 chars each). Default true.
shipping_locationNoDeliver-to country as an ISO code, e.g. 'PL': a foreign store then lists only items it delivers there, adds delivery cost to `delivery`, and usually prints prices already converted to PLN by Amazon (VAT of the destination). 'local' (or omitted) = the store's own country.

Output Schema

NameRequiredDescriptionDefault
fxYes
urlNo
asinYes
noteNo
brandNo
priceNo
queryYes
titleNo
ratingNo
sourceYes
reviewsNo
currencyNo
variantsNo
fetchedAtYes
price_plnNo
price_textNo
marketplaceYes
other_sellersNo
cheapest_offerNo
purchase_optionsNo
rating_histogramNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden well by disclosing cost and latency (one credit, ~10–25 s), marketplace override behavior, and a detailed result shape. It still omits some operational details such as authentication, error behavior, and the server-side cache behavior described in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and cost are front-loaded, but the description is a very long single paragraph with an extensive result-shape listing. Since an output schema already exists, much of the return-field enumeration is redundant and reduces conciseness.

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?

For a nine-parameter lookup tool with full schema coverage and an output schema, the description is largely complete: it explains the ASIN/URL input model, marketplace override, cost, latency, and output richness. Its main gap is explicit guidance on sibling-tool 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 description coverage is 100%, so the schema already documents all nine parameters. The description adds some semantic context about ASIN URLs and cross-store ASIN lookup, but most parameter meaning is carried by the schema rather than the description.

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 states a specific verb and resource: retrieve full details of one Amazon product by ASIN or product URL. It clearly scopes the tool to a single product lookup, which distinguishes it from broader search, comparison, and marketplace-list sibling tools.

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?

The description implies usage by explaining that it returns full details for one ASIN and that the same ASIN can be looked up on another store. However, it does not explicitly say when to use this instead of amazon_search, amazon_compare, or amazon_marketplaces, so routing remains mostly inferred.

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