Skip to main content
Glama
Sign In
Asin MCP Server

Asin MCP Server

by asindotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Track a product

track_product

Add Amazon ASINs or product links to a watchlist to monitor price changes, set target-price alerts, and schedule checks.

Instructions

Track a product. Adds an ASIN, an Amazon link or a short link (amzn.to, a.co…) to your watchlist. The first check runs in the background within seconds (checking is true until then): poll GET /products/{id}, or send wait: true to get the answer once it's d…

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": {
      "product": "<product>"
    },
    "name": "track_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoAnswer once the first check is done (up to 45 seconds) Default: false.
productYesASIN (B09DFCB66S) or Amazon product link
marketplaceNoAmazon store, e.g. com for amazon.com. A product link sets it on its own. Allowed values: com, co.uk, de, fr, it, es, ca, co.jp, com.br, com.mx, in. Default: "com".
target_priceNoEmail the owner when the price goes at or below this amount. null removes it.
interval_minutesNoMinutes between two checks (1440 = daily). Checks faster than daily need a plan or a credit pack: every 60 minutes with a pack or Starter, 30 with Pro, 5 with Business. Default: 1440.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only establish that this is a non-read-only, non-destructive, open-world write; the description adds substantive behavior the annotations cannot convey: the first check runs asynchronously in the background, checking is true until it finishes, and the caller can poll GET /products/{id} or pass wait:true. It falls short of a 5 only because the sentence is cut off, leaving the wait path's outcome incompletely specified.

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?

Front-loaded and dense: identity and accepted input formats come first, then the async checking contract. The truncated final clause is the only structural flaw; otherwise every sentence carries operational information.

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?

There is no output schema, so the description must explain what happens on return, and it does by describing the background check, the checking flag, and the wait:true alternative. The mid-sentence truncation leaves the wait path's completion behavior unresolved, and no guidance is given on how tracking interacts with sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by tying the async first-check behavior to the wait parameter and by naming the polling endpoint for the non-wait path. It does not elaborate on target_price or interval_minutes beyond what the schema already documents.

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?

States a specific verb and resource ('Track a product') and immediately clarifies what tracking means: adding an ASIN, Amazon link, or short link (amzn.to, a.co) to a watchlist. The accepted identifier formats distinguish it from siblings like check_product or update_product, which operate on already-tracked items.

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 gives clear guidance on the wait-vs-poll decision for the first check, which is useful. However, it never states when to choose track_product over siblings such as check_product, get_product, or update_product, so the broader routing decision is left to inference.

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