Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

amazon_product

Read-onlyIdempotent

Retrieve structured product data for any Amazon listing using its ASIN, including name, price, images, and reviews. Ideal for product monitoring and catalog enrichment.

Instructions

Retrieve parsed details for a single Amazon product by ASIN.

    Returns structured product data — name, brand, pricing, images, feature
    bullets, product information, review summary, category, coupon flags — for
    one Amazon listing, already parsed from the product page.

    When to use:
    - You have a specific ASIN and want its full structured details
    - Product monitoring, catalog enrichment, price/spec extraction

    When NOT to use:
    - You only have a search term, not an ASIN (use 'amazon_search' first)
    - You need the list of sellers/offers for the product (use 'amazon_offers')

    Args:
        params (AmazonProductParams): asin (required) plus optional tld,
            country_code, language, output_format, and include_html.

    Returns:
        str: JSON (default) or CSV containing the structured product data.

    Raises:
        ToolError: If the API key is missing, the rate limit is exceeded, or
            the request fails.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate a safe, read-only operation. The description adds behavioral context such as the parsed nature of the output, error conditions (ToolError for rate limits, missing API key), and the output format, without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, well-organized into sections, and front-loads the core action. Every sentence serves a purpose, with no wasted words.

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?

Given the tool has a comprehensive output schema and nested parameters, the description provides full context: use cases, alternatives, error handling, and supported formats, leaving no significant gaps.

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?

The description lists parameter names but does not add substantial meaning beyond the detailed input schema, which already describes each field. Schema coverage is effectively high, warranting a baseline of 3.

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?

The description clearly states the tool retrieves parsed details for a single Amazon product by ASIN, listing specific data fields. It distinguishes itself from siblings like 'amazon_search' and 'amazon_offers' with explicit usage guidance.

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

Usage Guidelines5/5

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

The description includes 'When to use' and 'When NOT to use' sections with concrete scenarios and alternative tool recommendations, providing strong decision support for the agent.

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/scraperapi/scraperapi-mcp'

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