Skip to main content
Glama

Scrapingdog

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Scrapingdog Amazon Product

scrapingdog_amazon_product
Read-onlyIdempotent

Get Amazon product data by ASIN via Scrapingdog — title, price, rating, review count, availability, feature bullets, and images as parsed JSON. Pass an asin (e.g. "B0BFC7WQ6R") or a full Amazon product url. Example: scrapingdog_amazon_product({ asin: "B0BFC7WQ6R", domain: "com", _apiKey: "your-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFull Amazon product URL — the ASIN is extracted from it. Alternative to `asin`.
asinNoAmazon ASIN (product identifier), e.g. "B0BFC7WQ6R". Provide this or `url`.
domainNoAmazon marketplace TLD, e.g. "com", "co.uk", "de", "in". Default "com".
_apiKeyYesBYOK Scrapingdog API key (free trial at scrapingdog.com)
countryNoISO country code for marketplace targeting, e.g. "us". Default "us" (1 credit; other countries cost 5).
languageNoISO 639-1 language code for product data, e.g. "en", "de". Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-scrapingdog-api-key",
+    "asin": "B0BFC7WQ6R"
+  },
+  {
+    "_apiKey": "your-scrapingdog-api-key",
+    "country": "gb",
+    "domain": "co.uk",
+    "url": "https://www.amazon.co.uk/dp/B0BFC7WQ6R"
+  }
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds value by specifying the returned data format (parsed JSON with fields like title, price, etc.), which goes beyond annotations.

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?

The description is two sentences plus a code example, which is concise and front-loaded. The example is helpful, though minor redundancy with schema examples could be trimmed.

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?

With no output schema, the description adequately explains return data. Parameters are fully covered by schema and description. The example demonstrates usage for common cases. Overall sufficient for a simple product lookup tool.

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% with clear parameter descriptions. The description adds an example call and clarifies the relationship between asin and url parameters, providing context beyond the schema alone.

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 clearly states the tool fetches Amazon product data by ASIN via Scrapingdog, listing specific fields (title, price, rating, etc.) and JSON output. It distinguishes from sibling scraping tools like scrapingdog_google_search by focusing on Amazon products.

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 provides an example call and mentions passing an ASIN or URL, but does not explicitly state when to use this tool versus alternatives like scrapingdog_scrape or other data retrieval tools. No 'when not to use' guidance is given.

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

All Scrapingdog 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