Skip to main content
Glama
oxylabs

Oxylabs MCP Server

Official
by oxylabs

amazon_product_scraper

Read-only

Scrape Amazon product data with keyword search, parsing, and localization options. Supports currency, geo-location, and auto variant selection for accurate pricing.

Instructions

Scrape Amazon products.

Supports content parsing, different user agent types, domain, geolocation, locale parameters and different output formats. Supports Amazon specific parameters such as currency and getting more accurate pricing data with auto select variant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword to search for.
autoselect_variantNoTo get accurate pricing/buybox data, set this parameter to true.
currencyNoCurrency that will be used to display the prices.
parseNoShould result be parsed. If the result is not parsed, the output_format parameter is applied.
renderNo Whether a headless browser should be used to render the page. For example: - 'html' when browser is required to render the page.
user_agent_typeNoDevice type and browser that will be used to determine User-Agent header value.
domainNo Domain localization for Google. Use country top level domains. For example: - 'co.uk' for United Kingdom - 'us' for United States - 'fr' for France
geo_locationNo The geographical location that the result should be adapted for. Use ISO-3166 country codes. Examples: - 'California, United States' - 'Mexico' - 'US' for United States - 'DE' for Germany - 'FR' for France
localeNo Set 'Accept-Language' header value which changes your Google search page web interface language. Examples: - 'en-US' for English, United States - 'de-AT' for German, Austria - 'fr-FR' for French, France
output_formatNo The format of the output. Works only when parse parameter is false. - links - Most efficient when the goal is navigation or finding specific URLs. Use this first when you need to locate a specific page within a website. - md - Best for extracting and reading visible content once you've found the right page. Use this to get structured content that's easy to read and process. - html - Should be used sparingly only when you need the raw HTML structure, JavaScript code, or styling information.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's mention of scraping is consistent. The description adds some behavioral context (e.g., auto select variant) but does not disclose any additional traits beyond what annotations provide. No contradiction.

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 covering key features without excessive verbosity. However, it could be slightly more structured and front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters with full schema coverage and an existing output schema, the description provides a decent overview. However, it lacks information on output format, error handling, or limitations, which is only partially compensated by the schema.

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 parameters. The description merely summarizes features without adding new semantic meaning beyond what is in the schema. No extra value added.

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 clearly states it scrapes Amazon products and lists supported features. However, it does not differentiate from sibling tools like amazon_search_scraper or universal_scraper, leaving some ambiguity about the specific use case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as amazon_search_scraper or universal_scraper. The description lists capabilities but lacks context on appropriate scenarios or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oxylabs/oxylabs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server