Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

amazon_offers

Read-onlyIdempotent

Retrieve structured seller offers for an Amazon product by ASIN, showing price, condition, seller rating, and Prime status for comparison and repricing analysis.

Instructions

Retrieve the parsed list of seller offers for an Amazon product.

    Returns structured offer listings for one ASIN — listing/shipping price,
    condition, seller name and rating, Prime/FBA flags, and delivery info —
    across the sellers offering that product.

    When to use:
    - Comparing sellers, prices, and conditions (new/used) for a known ASIN
    - Buy-box / third-party seller and repricing analysis

    When NOT to use:
    - You want the product's own details (use 'amazon_product')
    - You only have a search term (use 'amazon_search' to get the ASIN first)

    Args:
        params (AmazonOffersParams): asin (required) plus optional condition
            filters (condition, f_new, f_used_like_new, f_used_very_good,
            f_used_good, f_used_acceptable), tld, country_code, language, and
            output_format.

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

    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
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds details about return format (JSON/CSV) and error conditions (API key, rate limit, request failure), enhancing transparency.

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?

Well-structured with sections for purpose, usage, arguments, returns, and raises. No redundant sentences. Front-loaded.

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?

Covers usage context, alternatives, and error handling. With an output schema, return details are sufficient. Some aspects like pagination or offer count are absent but not critical.

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?

Description lists the parameters but relies on schema descriptions (which are present) for details. It adds minimal value beyond summarizing optional filters.

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 seller offers for an Amazon ASIN, listing specific fields. It distinguishes from siblings amazon_product and amazon_search.

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?

Explicit 'When to use' and 'When NOT to use' sections with named alternative tools for product details and search.

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