Skip to main content
Glama
oxylabs

Oxylabs MCP Server

Official
by oxylabs

amazon_search_scraper

Read-only

Extract Amazon search results by keyword with configurable category, merchant, currency, domain, and geolocation. Supports pagination, parsing, and output formats.

Instructions

Scrape Amazon search results.

Supports content parsing, different user agent types, pagination, domain, geolocation, locale parameters and different output formats. Supports Amazon specific parameters such as category id, merchant id, currency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword to search for.
category_idNoSearch for items in a particular browse node (product category).
merchant_idNoSearch for items sold by a particular seller.
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.
start_pageNoStarting page number.
pagesNoNumber of pages to retrieve.
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, indicating a safe read operation. The description adds some context about supported features (parsing, pagination) but does not disclose other behavioral traits like rate limits or response structure.

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 concise sentences with front-loaded purpose. No wasted words, but could be more structured with explicit parameter list or usage hints.

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 13 parameters, output schema, and siblings, the description covers main features but misses usage guidelines and behavioral details. Adequate but not fully comprehensive.

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 coverage is 100%, so parameters are fully described. The description groups features (e.g., 'pagination, domain, geolocation') but adds little meaning beyond the schema. Baseline of 3 is appropriate.

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?

Description clearly states 'Scrape Amazon search results' with a specific verb and resource. It distinguishes from siblings like 'amazon_product_scraper' and 'google_search_scraper' by targeting Amazon search specifically.

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?

Description implies usage for Amazon search but does not explicitly state when to use or avoid this tool vs alternatives. No guidance on prerequisites or boundary conditions.

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