Skip to main content
Glama
Sign In
Asin MCP Server

Asin MCP Server

by asindotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List tracked products

list_products
Read-only

Retrieve tracked Amazon products from your watchlist, newest first, with each item's latest state, recent price trend, and filters for ASIN, marketplace, or app tab.

Instructions

List tracked products. Your watchlist, newest first, with each product's latest state and its recent prices (trend). Filter with asin (and marketplace) to know if a product is tracked, or with filter to get the same lists as the app's tabs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
asinNoOnly this ASIN
pageNoPage number Default: 1.
limitNoProducts per page Default: 20.
filterNoOnly the products of one of the app's watchlist filters. all: Every tracked product (default). drops: Cheaper now than when the product was added. target: At or below its target price. out_of_stock: No offer at the last check. attention: The last check didn't go through (last_error is set): no cred… Allowed values: all, drops, target, out_of_stock, attention, paused. Default: "all".
marketplaceNoOnly this Amazon store Allowed values: com, co.uk, de, fr, it, es, ca, co.jp, com.br, com.mx, in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 value beyond them by disclosing result ordering (newest first) and payload contents (latest state plus recent price trend), which matters because no output schema exists. It says nothing about pagination behavior or result-set limits, which keeps it below a 5.

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 front-loaded sentences with no filler; the core capability comes first and usage hints follow. The second sentence is heavily parenthetical ("(and marketplace)", "(trend)"), which makes it slightly denser than it needs to be.

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?

For a list tool with no output schema and no required parameters, the description covers what comes back, in what order, and the two filtering intents. Pagination via page/limit is left entirely to the schema, and the partially truncated enum text for the 'attention' filter is not compensated for, which is a small remaining gap.

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 baseline is 3. The description goes further by explaining the intent behind asin (an existence check for tracking) and pairing it with marketplace, and by framing filter as the app's tab semantics rather than a bare enum.

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?

Names a specific verb and resource ("List tracked products") and immediately characterizes the result set: the user's watchlist, ordered newest first, each with latest state and recent prices. That is enough to separate it from single-product siblings like get_product or check_product, though 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 Guidelines4/5

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

Gives concrete when-to-use routing for the two main query modes: pass asin (plus marketplace) as a tracked/not-tracked lookup, or use filter to reproduce the app's tab lists. It stops short of stating when to prefer a sibling tool such as get_product for full detail, so it is clear context without explicit alternatives.

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