Skip to main content
Glama
Sign In
Asin MCP Server

Asin MCP Server

by asindotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Offers already known

get_offers
Read-only

Retrieve known seller offers and prices for an Amazon ASIN, including Amazon's own price and cheapest new or used options, without reading Amazon or spending a credit.

Instructions

Offers already known. Who sells the product and at what price, as last read, cheapest first, with Amazon's own price and the cheapest new and used offers (used is only known for Amazon's own outlet). Free: this never reads Amazon or spends a credit. When nobody…

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_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinYes10-character ASIN
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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description still adds real context: results are stale ('as last read'), ordered cheapest-first, used offers are only known for Amazon's own outlet, and no credit is spent. The only gap is that the truncated final sentence withholds whatever behavior it was about to disclose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The ordering information is front-loaded well, but the middle is a run-on em-dash sentence mixing several ideas, and the final sentence is truncated mid-thought, leaving dangling text rather than an earned ending.

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 two-parameter read-only tool with no output schema, the description covers source, ordering, and cost, which is largely sufficient. But it ends abruptly ('When nobody…'), so an agent cannot know the intended fallback or empty-result behavior.

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%, with asin and marketplace fully documented including allowed values and default, so the baseline applies. The description adds no parameter-level detail (e.g., how marketplace affects cached results) beyond the schema.

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 the resource specifically ('Offers already known. Who sells the product and at what price') and adds ordering (cheapest first) and scope of included offers. It implicitly distinguishes itself from the fetching sibling by emphasizing cached, last-read data, though it never names fetch_offers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Free: this never reads Amazon or spends a credit' gives a clear condition favoring this tool over a live-fetch alternative, letting an agent infer to prefer it when cached data suffices. However, the trailing 'When nobody…' clause where exclusions/alternatives likely lived is cut off, so the when-not guidance is incomplete.

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