Skip to main content
Glama
Sign In
Asin MCP Server

Asin MCP Server

by asindotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Price history of any ASIN

get_asin_history
Read-only

Retrieves recorded price history for an ASIN over a chosen period on an Amazon marketplace, returning prices oldest first with lowest, highest, and average values.

Instructions

Price history of any ASIN. Every price Asin read for an ASIN on a marketplace over the period, whoever tracks it, oldest first, with the lowest, highest and average of those prices. A history of more than 5000 points is thinned evenly, keeping its first and last poi…

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

Input Schema

NameRequiredDescriptionDefault
asinYes10-character ASIN
daysNoHistory period in days Default: 90.
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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are ordered oldest first, include lowest/highest/average aggregates, and any series over 5000 points is evenly thinned while preserving first and last points — critical for an agent interpreting completeness of results.

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 content is dense and front-loaded with the resource and scope, which is good. However, the text ends mid-sentence ('keeping its first and last poi…'), leaving a dangling thought, and the aggregate/thinning details could be split into clearer clauses.

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 no output schema, the description carries the burden of describing the return value, and it does so well: price points, ordering, and min/max/average aggregates. Gaps remain around currency/marketplace semantics and whether the 5000-point thinning affects the reported aggregates, and the truncation leaves the final clause unresolved.

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 all three parameters documented, so the baseline is 3. The description only loosely gestures at the parameters ('on a marketplace over the period') and adds no format, default, or edge-case meaning beyond the schema, such as how negative or very large 'days' values behave.

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?

The description names a specific verb and resource ('Price history of any ASIN') and explains the scope: every price read for an ASIN on a marketplace over a period, regardless of which source tracks it. That scope implicitly separates it from siblings like get_offers or check_product, but no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no reference to the alternatives (get_offers, fetch_offers, check_product) that an agent must choose between. Usage is only inferable from the stated purpose, and the description never says when a live offer lookup is preferable to a historical pull.

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