The two synchronous tools answer the questions you ask once: amazon_product for the detail behind an ASIN, amazon_search for where listings actually rank on a keyword. Anything larger goes through amazon_batch_create, which takes ASINs or search queries and hands back a batch id; from there it is either amazon_batch_status on a poll or the webhook_url firing when the job lands. The domain and language arguments are what select the marketplace, so the same ASIN can be pulled for more than one storefront.
An Amazon product data API client covering 4 tools: two synchronous lookups and an async batch queue with a webhook callback.
- One product at a time: amazon_product returns roughly 55 fields for an ASIN, including title, price, variations, reviews, the category ladder and images, on a chosen domain and language.
- Keyword results as ranked data: amazon_search returns product listings with organic and sponsored positions, prices, ratings and image URLs, with sort_by, pages and start_page controlling the sweep.
- Volume without waiting on it: amazon_batch_create queues up to 1000 ASINs or search queries against either endpoint and returns a batch id, with an optional webhook_url for the callback.
- Progress you can poll: amazon_batch_status reports how far an async batch has got and returns its results.
An API key for the service in ASA_API_KEY, and — if you want the callback rather than polling — a webhook_url the service can reach.
One command plus a key — npx -y amazon-scraper-api-mcp, then supply credentials