Skip to main content
Glama

Amazon product details

get_amazon_product_details
Read-only

Scrape Amazon product details using ScrapingBee.

Scope: one query per call. To run many queries in one pass, or to write results to disk instead of into the conversation, use the ScrapingBee CLI — scrapingbee <command> --input-file queries.txt --output-dir results.

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": {
      "query": "<query>"
    },
    "name": "get_amazon_product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoResponse-header label only.
queryYesSearch term (must be a valid 10-character ASIN code)
domainNoThe Amazon domain to use for the search (e.g., com, co.uk, de).
countryNoThe country code for localization (e.g., us, uk, de). Do not combine with a matching domain (e.g., country=fr&domain=fr).
add_htmlNoWhether to return the HTML along with the product details.
currencyNoThe currency code (ISO 4217) to display results (e.g., USD, GBP, EUR).
languageNoThe language code to display results (e.g., en, fr, de).
zip_codeNoThe zip code to use for delivery localization.
screenshotNoForce a browser screenshot (returns base64 image).
light_requestNoWhether to use a light request or not.
autoselect_variantNoWhether to automatically select product variant if applicable.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description correctly does not contradict it. It adds a real behavioral trait beyond annotations: a hard one-query-per-call limit and where results land (the conversation). It says nothing about credit consumption, rate limits, or failure behavior when the ASIN is invalid, which matters for a scraping tool.

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?

Purpose is front-loaded in one sentence, followed by the scope constraint and the escape hatch to the CLI; no filler or repetition of schema content. The CLI invocation excerpt is the only slightly bulky element, but it earns its place by showing the exact flag shape.

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 11 parameters fully documented in the schema and an output schema present, the description need not explain return values. It covers the two things structured fields cannot: the single-query-per-call constraint and the recommended path when that constraint is a problem, which is sufficient for correct invocation.

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 all 11 parameters (query, domain, country, currency, screenshot, etc.) are already documented with examples in the schema. The description adds no parameter-level meaning such as which combinations are valid or how screenshot interacts with light_request, so the baseline of 3 applies.

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 first sentence gives a specific verb and resource ("Scrape Amazon product details") plus the backing service, which cleanly separates it from Walmart/YouTube/Google siblings. It does not distinguish itself from closer neighbors like get_amazon_pricing or get_amazon_search_results, so an agent must infer that this one returns a single product's detail payload.

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?

The description explicitly states the operating scope ("one query per call") and names a concrete alternative for the batch case (the ScrapingBee CLI with --input-file/--output-dir), including the reason to choose it (write to disk instead of into the conversation). It stops short of guidance against sibling tools such as get_amazon_pricing, so it is clear context rather than full when/when-not coverage.

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