Amazon Price Tracker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_product_priceA | Get Amazon product price history and current pricing from camelcamelcamel.com. Input: Amazon URL (amazon.com/dp/ASIN), short share link (a.co/d/xxx), camelcamelcamel URL, or a bare 10-char ASIN. Returns: current price, all-time lowest/highest, average price, and product details. |
| resolve_short_linkA | Resolve an Amazon short link (a.co, amzn.to) to the full Amazon URL and extract the ASIN. |
| extract_asinA | Extract the ASIN from any Amazon URL format. Works with full URLs, short links, and camelcamelcamel URLs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The primary tool get_product_price accepts all input formats directly, including short links and URLs, making the auxiliary tools unnecessary in many cases. resolve_short_link and extract_asin both extract ASINs from links, with only slight differences in input flexibility, so agents may struggle to choose the right tool for a given URL. This overlapping functionality creates ambiguity in tool selection.
All three tools follow a consistent verb_noun pattern with lowercase snake_case: get_product_price, resolve_short_link, extract_asin. This makes the API predictable and easy to navigate.
Three tools is a minimal but reasonable number for a price-tracking server. However, since get_product_price already handles all input formats, the two preprocessing tools appear somewhat redundant, making the count slightly higher than necessary.
The server covers the core operation of retrieving price history and current pricing for a given product. It lacks batch lookup or search features, but for its narrow purpose of single-product tracking, it provides a complete workflow.