Skip to main content
Glama

ScraperAPI (Unofficial)

Scraperapi Amazon Product

scraperapi_amazon_product
Read-onlyIdempotent

Get structured Amazon product data by ASIN, title, price, rating, reviews count, features, images, availability. Example: scraperapi_amazon_product({ asin: "B0BFC7WQ6R", country: "us", tld: "com", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asin": "B0BFC7WQ6R",
      "_apiKey": "your-scraperapi-api-key"
    },
    "name": "scraperapi_amazon_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldNoAmazon marketplace top-level domain, e.g. "com", "co.uk", "de". Optional (default com).
asinYesAmazon ASIN (product identifier), e.g. "B0BFC7WQ6R"
_apiKeyYesScraperAPI key
countryNoTwo-letter country code for proxy geotargeting, e.g. "us", "gb". Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, openWorld=true, destructive=false, so the safety profile is fully covered. The description adds the concrete shape of the returned data (price, rating, reviews, features, images, availability), which matters because there is no output schema. It says nothing about credit consumption, rate limits, or failure behavior when a product/ASIN is missing.

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?

Two sentences, front-loaded with the outcome and followed by a compact example. The example largely duplicates the schema's own examples array, which is mild redundancy, but nothing is padded or vague.

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 four-parameter read-only lookup with no output schema, enumerating returned fields, showing a working example, and leaving safety to annotations covers what an agent needs to call it correctly. Remaining gaps are operational details (cost, error on invalid ASIN) rather than invocation blockers.

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%, with asin, country, tld, and _apiKey all documented inline, so the baseline of 3 applies. The description adds no semantics beyond the schema — it repeats the ASIN example and shows a sample call whose defaults (country/tld) are already explained in the property descriptions.

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?

States a specific verb+resource ("Get structured Amazon product data") and anchors it to an ASIN-keyed lookup that implicitly separates it from the sibling scraperapi_amazon_search. It also enumerates the returned fields, so an agent knows exactly what it gets back. It stops short of explicitly naming a sibling to contrast with.

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 example invocation and the "by ASIN" framing imply the use case (retrieve one known product), but there is no explicit when-to-use/when-not guidance and no mention of scraperapi_amazon_search for keyword-based discovery. An agent must infer the selection rule from the parameter name alone.

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.