Amazon Product, Price, and Stock Tracker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token, available from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| track_amazon_productsA | Read the current Amazon buy box price, list price, stock status, seller, and rating for ASINs or product URLs on 9 marketplaces, priced for that marketplace's delivery country. Keeps the last reading between runs and returns a change row when a price moves or a product goes out of or back into stock. Costs 0.0056 USD per product on amazon.com and amazon.ca, 0.015 USD elsewhere, plus a run start. |
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 1 tool
There is only one tool, so there is no possibility of selecting the wrong one or confusing it with a sibling. Its purpose — read price/stock for Amazon ASINs and report changes — is unambiguous.
The single name follows a clear verb_noun snake_case convention (track_amazon_products) that is descriptive and readable. A single data point makes it hard to demonstrate consistency across the set, but nothing deviates.
One tool is defensible for a narrowly scoped read-only tracker, but it is thin — everything the server does is funneled through a single call with no complementary operations. It sits at the borderline of the 1-2 tools 'feels thin' band.
The core read-and-diff operation is covered, including state persistence and change reporting. However, a 'tracker' surface lacks obvious companions: listing currently tracked ASINs, retrieving price history over time, setting alert thresholds, or removing a product from tracking are all unavailable.