Skip to main content
Glama
Sign In
Scrapingdog MCP Server

Scrapingdog MCP Server

by Darshan972
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Amazon Offers API

amazon_offers

Retrieve all buying offers and sellers for any Amazon product using its ASIN. Specify domain and country to get marketplace-specific results.

Instructions

Fetch all buying offers and sellers for an Amazon product by ASIN.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asin": "<asin>"
    },
    "name": "amazon_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinYesAmazon ASIN of the product.
domainNoAmazon TLD, e.g. com, in, de, co.uk. (API default: com)
countryNoTwo-letter ISO marketplace country code. (API default: us)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only says 'Fetch', implying a read-only operation, but does not mention what 'all' means (e.g., pagination), how domain/country affects results, or any error behavior. This is sparse for a tool with no annotation support.

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 a single, well-structured sentence that immediately states the action and resources. No unnecessary words or repetition.

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?

For a simple 3-parameter tool, the description gives the core functionality but omits information about the return format, the exact effect of optional parameters, and whether 'all' implies pagination. Given no output schema and no annotations, the description is adequate but not thorough.

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%, with each parameter described. The description adds no extra meaning beyond the schema, so the 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?

The description uses a specific verb ('Fetch') with a clear resource ('all buying offers and sellers') and identifies the key input ('by ASIN'). It distinguishes this tool from siblings like amazon_product or amazon_reviews, which focus on other product aspects.

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?

The description implies when to use the tool (when offers/sellers are needed) but provides no explicit guidance on when not to use it or alternatives. With many sibling tools, this lack of differentiation guidance is a gap, though the purpose is clear enough to infer basic use.

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

Deploy Server

Other Tools