Skip to main content
Glama

amazon_offers

Retrieve all active offers for an Amazon ASIN, including pricing, seller details, delivery options, and availability in a single response.

Instructions

Retrieves detailed offer data for a given ASIN — every active offer with pricing, availability, seller details, and delivery options. [Credits: Not explicitly stated on the documentation page.] Notes: No pagination applicable — returns all active offers for the ASIN in a single response (offers_count / total_offers reflect the returned set). Returns: { title, rating, reviews_total, image, asin, link, offers_count, total_offers, offers: [{price:{symbol,value,currency,raw}, minimum_order_quantity:{value}, maximum_order_quantity:{value}, condition:{is_new,title}, delivery:{fulfilled_by_amazon,date,comments,price:{...}}, seller:{name,link,id,rating,ratings_total,ratings_percentage_positive}, offer_id, is_prime, position, buybox_winner, offer_asin, is_pinned}] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asinYesThe Amazon Standard Identification Number (ASIN) of the product whose offers you want to retrieve. Example: B0BZXDFGSJ.
domainYesThe Amazon domain to scrape. Pass the TLD only — e.g. com, co.uk, de, co.jp. See Amazon Supported TLDs doc for the full list.
countryYesISO country code for targeting a particular country. Affects price, delivery estimates, and offer availability. See Amazon Supported Countries doc for the full list. (default: us)
postal_codeNoZIP / postal code for hyper-local delivery filtering. When set, the API returns shipping dates and fees specific to that location.
Behavior3/5

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

With no annotations, description carries full burden. Discloses no pagination and returns all active offers, also provides return structure. However, lacks disclosure of whether tool is read-only, auth needs, rate limits, or other behavioral traits.

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?

Description is relatively concise, front-loading purpose. Includes helpful notes on credits and pagination with return structure example. A few extra details could be trimmed but overall efficient.

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?

Given absence of output schema, description compensates by providing detailed return structure. Covers key aspects like no pagination and credit note. Adequate for a single-resource tool with 4 parameters.

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 baseline 3. Description does not add much beyond schema for parameters; it mentions 'for a given ASIN' but schema already describes asin. No additional semantic enrichment for parameters.

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 uses specific verb 'Retrieves detailed offer data for a given ASIN' combined with resource 'ASIN' and includes key aspects like pricing, availability, seller details, delivery. Clearly distinguishes from sibling tools like amazon_product (product details) and amazon_reviews (reviews).

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?

Implies usage when needing offer data for a specific ASIN, mentions no pagination and returns all active offers, but does not explicitly state when to use vs alternatives or when not to use.

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/alessandrobenigni/ScrapingDog-MCP'

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