Skip to main content
Glama
Sign In
ScrapeUnblocker MCP Server

ScrapeUnblocker MCP Server

Official
by ScrapeUnblocker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Scrape an Amazon product page

amazon_product
Read-only

Retrieve detailed JSON data for one Amazon product, including price, availability, variants, seller, ratings, and reviews, by ASIN or product URL.

Instructions

Fetches a single Amazon product and returns it as JSON: title, brand and brandStoreUrl, parentAsin, manufacturer, modelNumber, partNumber, productCodes (UPC, EAN, GTIN, ISBN), condition, the amazonsChoice, bestSellerBadge, deal and coupon markers, price + currency, listPrice, savingsPercent and savingsAmount, unitPrice, subscribeAndSavePrice, shippingPrice, recentSales, availability (+ a boolean inStock), maxOrderQuantity, rating, reviewCount, ratingDistribution (percent per star), reviewSummary, seller, sellerUrl, sellerId, shipsFrom, fulfilledByAmazon, prime, delivery, returnPolicy, offersCount and offersFromPrice, bestSellersRank, features (bullet points), categories (breadcrumb), description, fromTheManufacturer and fromTheBrand (text and images), importantInformation, ingredients, whatsInTheBox, documents, warrantyAndSupport, productDetails, productOverview, dimensions, weight, dateFirstAvailable, variantDimensions and variants (each with its own ASIN and options), sustainability, protectionPlans, newerModel, sponsoredProducts, relatedProducts, images (the whole gallery) and videos. A field the page does not show is null or empty. Identify the product with either asin (plus marketplace) or a full product url. Other sellers' full offers are not on the product page: only their count and lowest price are returned here, /marketplace/amazon-offers lists them. prime and delivery are what a visitor who is not signed in sees. Amazon prices each page in the currency of the delivery location it infers from the visitor's IP address, so proxy_country defaults to the marketplace's home country (amazon.com -> US) and the call is routed through proxies in that country. The country of the proxy that served the request is reported as exitCountry. Returns JSON. Billed like an API request; listing plugins bill one unit per result page they fetch, so keep max_results modest.

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
urlNoFull Amazon product url, e.g. 'https://www.amazon.de/dp/B0BSHF7WHW'. The ASIN and marketplace are read from it, so `asin`/`marketplace` are not needed when a url is given.
asinNoAmazon product id (10-char ASIN, e.g. 'B0BSHF7WHW'; books use their ISBN-10). Give either `asin` (with `marketplace`) or a full `url`.
marketplaceNoRegional Amazon site the ASIN belongs to. Prices and currency differ per marketplace. One of: amazon.com, amazon.co.uk, amazon.de, amazon.fr, amazon.it, amazon.es, amazon.nl, amazon.se, amazon.pl, amazon.com.be, amazon.com.tr, amazon.ca, amazon.com.mx, amazon.com.br, amazon.co.jp, amazon.in, amazon.ae, amazon.sa, amazon.sg, amazon.com.au. Default: amazon.com.
proxy_countryNoProxy country the request is sent from (ISO-2, e.g. 'US', 'DE'). Defaults to the marketplace's home country so the price comes back in the expected currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.5
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.4.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses that missing page fields come back null or empty, that `prime`/`delivery` reflect a signed-out visitor, that pricing is geo-inferred via proxy country and reported as `exitCountry`, and that calls are billed per request. That is exactly the operational context an agent needs before spending a call.

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?

Front-loaded with the core statement, and the long field enumeration is justified because there is no output schema to document the return shape. The tail-end billing sentence about `max_results` is irrelevant here and slightly dilutes an otherwise tight structure.

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 and four optional parameters, the description carries the full burden and does: it documents the return payload, the null convention, product identification modes, proxy/currency behavior, and the boundary against the offers endpoint. Nothing material is left for the agent to guess.

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 real meaning beyond it — how `proxy_country` determines inferred delivery location, currency, and `exitCountry`, and how `asin`/`marketplace` become redundant when `url` is supplied. Minor flaw: the closing billing note tells the reader to 'keep max_results modest', a parameter this tool does not have, which is noise for this 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?

Opens with a specific verb and resource ('Fetches a single Amazon product and returns it as JSON'), then enumerates the returned payload so the agent knows exactly what the tool produces. It is clearly distinguishable from siblings like amazon_search or amazon_reviews, and it explicitly names the /marketplace/amazon-offers endpoint as the different tool for full seller offers.

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?

Gives concrete selection rules: identify the product with either `asin` + `marketplace` or a full `url`, and route to amazon-offers when full third-party offers are needed. It stops short of explicitly contrasting against amazon_search (search vs. single-product fetch), leaving that inference to the agent.

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

Deploy Server

Other Tools