Skip to main content
Glama

Amazon pricing

get_amazon_pricing
Read-only

Retrieve current Amazon product pricing and seller offers for a given ASIN.

Scope: one query per call. To run many queries in one pass, or to write results to disk instead of into the conversation, use the ScrapingBee CLI — scrapingbee <command> --input-file queries.txt --output-dir results.

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": "get_amazon_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoResponse-header label only.
asinYesRequired 10-character ASIN from an Amazon product URL.
domainNoAmazon domain (default com).com
countryNoISO country code for localization. Do not combine with a matching domain (e.g., country=fr&domain=fr).
add_htmlNoInclude page HTML in the response.
currencyNoISO 4217 display currency.
languageNoISO language code.
zip_codeNoZIP code for delivery localization.
light_requestNoUse a light request (default True) or browser-rendered (False).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context beyond that. It contributes the one-query-per-call batching limitation and the batch alternative, which are genuinely useful, but says nothing about latency, rate limits, or how seller offers vary (e.g. per-domain/localization effects) — the schema and annotations carry the rest.

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?

Three short sentences, with the purpose front-loaded ahead of the scope note and the batch alternative. The CLI sentence is slightly tangential for a single-call tool but is short and actionable, so nothing reads as padding.

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?

With an output schema present and full parameter documentation, the description does not need to describe return values, and it covers the main operational caveat (one query per call). For a read-only 9-param tool this is close to sufficient; the only real gap is the absence of routing guidance relative to the sibling Amazon tools.

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 the baseline of 3 applies; each of the 9 parameters already has a described default and meaning. The description adds no parameter-level insight such as how domain/country/zip_code interact for localization or when light_request=false is required to get offers — the one nuance that would have compensated meaningfully is absent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Retrieve current Amazon product pricing and seller offers for a given ASIN" gives a specific verb (retrieve) plus the exact resource (pricing and seller offers) and the keying input (ASIN). The pricing/offers framing is narrow enough to separate it from get_amazon_product_details, though it never explicitly names that sibling to anchor the distinction.

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 sets a clear operating constraint — "one query per call" — and routes high-volume work to the ScrapingBee CLI with a concrete `--input-file` / `--output-dir` invocation. What it omits is guidance on when to choose this instead of the other Amazon tools (product details, search results), so the when-not case is only implied by scope.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources