Skip to main content
Glama
Sign In
Asin MCP Server

Asin MCP Server

by asindotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Read every offer from Amazon

fetch_offers

Read every offer from Amazon for an ASIN, returning a recent cached result when available and refreshing on demand to check current seller offers and pricing.

Instructions

Read every offer from Amazon. Reads the offers on Amazon for 1 credit, refunded if it doesn't answer. A read made in the last 3 hours, by anyone, is returned instead, for free (charged: false). The answer is the same as GET /offers.

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

Input Schema

NameRequiredDescriptionDefault
asinYes10-character ASIN
refreshNoRead Amazon again unless the last read is under 5 minutes old (1 credit) Default: false.
marketplaceNoAmazon store, e.g. com for amazon.com Allowed values: com, co.uk, de, fr, it, es, ca, co.jp, com.br, com.mx, in. Default: "com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the cost model (1 credit), the refund condition, the 3-hour cross-user cache that returns a free prior read with charged: false, and the refresh override. The only friction is that the description's read framing sits uneasily with readOnlyHint=false, though the credit charge itself explains that flag rather than contradicting it. What it does not cover is failure behavior or how the charge interacts with the refresh flag's 5-minute window.

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 tightly packed sentences with the purpose front-loaded and no filler. The trailing reference to GET /offers is the weakest sentence, since it outsources meaning to an external specification the agent may not hold.

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 paid, cached read tool with no output schema, the description covers cost, caching, and refunds well. It is incomplete on the two things an agent most needs: what fields an offer record contains, and how this differs from the very similar sibling get_offers.

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%, so the schema already documents asin, refresh, and marketplace, and usage of those parameters is fully derivable there. The description adds caching economics that bear on refresh, but it introduces a 3-hour window that is not obviously reconciled with the schema's 5-minute refresh threshold, which adds mild ambiguity rather than clarity.

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?

States a specific verb and resource ("Read every offer from Amazon") and the scope (every offer, by ASIN on a marketplace). It does not differentiate itself from the sibling get_offers, and the closing line "The answer is the same as GET /offers" points at an external API rather than at the sibling tool, so an agent cannot tell the two apart from the description alone.

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?

Implied usage is clear enough (fetch full offer data for one ASIN), and the description adds useful context about the free cached read and when a charge applies. It never says when to prefer this over get_offers, check_product, or search_amazon, and it gives no prerequisites or exclusions, leaving the agent to infer tool selection.

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