Skip to main content
Glama
E-commerce Search & Rankings MCP

E-commerce Search & Rankings MCP

Amazon Product Scraper

junglee--Amazon-crawler
Read-only

Scrape Amazon product, search, and category URLs to extract prices, ASINs, ratings, reviews, and descriptions into structured JSON without the Amazon API.

Instructions

Amazon Product Scraper. Use this Amazon scraper to collect data based on URL and country from the Amazon website. Extract product information without using the Amazon API, including reviews, prices, descriptions, and Amazon Standard Identification Numbers (ASINs). Download data in various structured formats.

When to use: Use when you need Amazon product details or search/category results (title, price, ASIN, rating, reviews count) from product, search or category URLs.

Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset.

Behavior: starts one run of the Apify Actor "junglee/Amazon-crawler" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/junglee/Amazon-crawler

Input Schema

NameRequiredDescriptionDefault
zipCodeNoThe zip code to use as the delivery location. This is useful for more precise location settings, especially in larger countries.
languageNoLanguage to use on Amazon. **Disclaimer**: each Amazon domain has a different set of supported languages. If you choose a language that is not supported by the domain, the scraper will use the default language of the domain.
maxOffersNoEnter the maximum number of offers you want to scrape per each product. This will let the scraper know when to stop. Note that this **will increase the number of requests** and **extend the scraping time**.
countryCodeNoThe country code to use as the delivery location.
proxyCountryNoYou can set proxy country to **avoid geo-blocking** and **access region-specific content**. Amazon shows you the products that can be shipped to your address based on the proxy you use. *By default*, the scraper **automatically selects** the **proxy country** based on the used Amazon website domain, ensuring low blocking rates and results relevant to the base domain.AUTO_SELECT_PROXY_COUNTRY
scrapeSellersNoEnable this option to extract further information about sellers of the product. Scrapes the featured offer seller (main seller). This option goes hand in hand with the `maxOffers` option bby scraping the seller of each offer. If you set `maxOffers` to 0, only the featured offer seller will be scraped. Note that this **will increase the number of requests** and **extend the scraping time**.
useCaptchaSolverNoIf enabled the scraper will automatically solve captchas thrown by Amazon. This will decrease the amount of request retries and increase the speed of the scraper. ***IMPORTANT*** - This option works well only for the `'.com'` Amazon domain, but even for that one Amazon doesn't show a few product fields after solving a captcha (specifically: 'attributes', 'manufacturer attributes', and 'bestseller ranks')
maxItemsPerStartUrlNoEnter the maximum number of results you want to scrape per each star URL. This will let the scraper know when to stop. Example: 100
scrapeProductDetailsNoIf enabled, the scraper will extract each found product from the category page in detail (this is the default behavior). If disabled, the scraper will only extract the quick product information from the category page. Useful for faster and more lightweight searches for products.
categoryOrProductUrlsYesUse a link to the Amazon category you want to scrape, e.g. video games - https://www.amazon.com/s?bbn=16225016011&rh=n%3A20972781011, https://www.amazon.com/dp/B0B3BVWJ6Y. You can also filter within the category with almost any filter available, i.e. price, manufacturer, rating, etc. By using a different URL you can also choose a different Amazon country, e.g. Germany: https://www.amazon.de/. You don't need to set a proxy country to do that. Example: [{"url":"https://www.amazon.com/s?k=keyboard…
locationDeliverableRoutesNoThe list of routes/page types, for which the deliverable location settings should be applied. - This is useful for speeding up the scraping process by not applying the location settings to all pages, for which you don't need the localized data for. - For example, you can set it to `['SEARCH', 'PRODUCT']` to apply the location settings only to search and product pages. - By default, all pages are included.
maxSearchPagesPerStartUrlNoEnter the maximum number of search pages to scrape for each start URL. E.g. only scrape the first 5 pages. This field can also be used with the `maxItemsPerStartUrl` option, the scraper will stop after either one of these limits is reached. Example: 9999
scrapeProductVariantPricesNoEnable this option to extract prices of different variations of a product. Useful when you need prices for each variant. Note that this **will increase the number of requests** and **extend the scraping time**.
maxProductVariantsAsSeparateResultsNoEnter the maximum number of product variants you want to scrape per each product, outputted as separate results. **Please beware** that **you can already get** most of the **variant details** changes, in the **`variantDetails` field**, which is outputted by default. Note that this **will increase the number of requests** and **extend the scraping time**. Example: 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld, non-idempotent, and non-destructive behavior, and the description adds meaningful context beyond them: each call starts one run of the Apify Actor through the mcp.apify.com gateway, consumes the caller's own APIFY_TOKEN and Apify account, and only reads public data. It does not mention cost/credit consumption or run duration, so it stops short of a 5.

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 front-loaded into 'When to use', 'Returns', and 'Behavior' sections, making it easy to scan. The opening sentence partially duplicates the title, and the docs URL at the end is filler but harmless.

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 14-parameter scraper with no output schema, the description explains what comes back (dataset rows as JSON, one per result, plus run and dataset IDs for paging), how the run is executed, and the auth requirement. It does not say how the caller should page the full dataset or what happens on long runs, so it is strong but not exhaustive.

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 14 parameters, including enums and their defaults; the baseline of 3 applies. The description only echoes 'URL and country' and adds no guidance on interplay between options such as maxOffers, scrapeProductDetails, or proxyCountry.

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 description states a specific verb and resource: scrape Amazon product, search, or category URLs and extract reviews, prices, descriptions, and ASINs without the Amazon API. The title plus the enumeration of extractable fields clearly separates it from siblings like the eBay, Walmart, and AliExpress scrapers. It loses a point only because the opening sentence ('collect data based on URL and country') is vaguer than the details that follow.

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?

An explicit 'When to use' section names the exact trigger: needing Amazon product details or search/category results from product, search, or category URLs. It gives a clear context but never names an alternative tool or states when NOT to use this one, which keeps it from a 5.

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