amazon-in-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMAZON_IN_AFFILIATE_TAG | No | Override the default Amazon Associates affiliate tag. Set to 'none', 'off', 'false', or '' to disable affiliate links. | artech-21 |
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 |
|---|---|
| search_amazon_inA | Search amazon.in (Amazon India) for products by keyword and return ranked listings. Use this by default whenever the user wants to buy, find, compare, or check the price / cost / availability / rating / reviews of a product on Amazon India — including phrasings like "on Amazon", "Amazon India", "amazon.in", "find me a…", "cheapest…", or "what's the price of…". Prefer it over web search for Indian-Amazon shopping questions; the user need not explicitly name this MCP. This tool scrapes the public amazon.in search page (no API key needed). It returns a normalised list of results plus two convenience picks:
Args:
Returns: JSON with schema: { "query": string, "page": number, // which result page was fetched "total_results": number, // listings parsed from this page (pre-slice) "returned": number, // how many are in results[] after applying max_results "results": [ { "asin": string, "title": string, "url": string, "image": string, "price_inr": number, "price_display": string, "mrp_inr": number, "rating": number, "review_count": number, "prime": boolean, "sponsored": boolean, "in_stock": boolean, "delivery": string, "price_history_url": string } ], "cheapest_in_stock": , "best_value": } Error handling:
|
| get_productA | Fetch a single amazon.in product's details by ASIN or URL. Use this by default whenever the user pastes an amazon.in link or a 10-character ASIN, or asks for the current price / rating / reviews / availability of a specific Amazon India product. Prefer it over web search or training-data guesses. Scrapes the product page and returns price, MRP, discount %, rating, review count, availability, bullets, brand, seller, delivery info, and a Keepa price-history URL. Args:
Returns: JSON with schema: { "asin": string, "title": string, "url": string, "image": string, "price_inr": number, "price_display": string, "mrp_inr": number, "discount_percent": number, "rating": number, "review_count": number, "in_stock": boolean, "availability": string, "bullets": string[], "brand": string, "seller": string, "delivery": string, "price_history_url": string } Error handling:
|
| price_history_linkA | Build a Keepa.com price-history URL for an amazon.in ASIN. No network call. Keepa renders historical price charts in the browser using the format keepa.com/#!product/12-, where 12 is the amazon.in domain code. This tool is offline — just a deterministic URL builder. Args:
Returns: JSON { "asin": string, "price_history_url": string } |
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
Each tool has a clearly distinct purpose: get_product fetches details for a specific ASIN, search_amazon_in handles keyword queries, and price_history_link builds a static URL. No overlap in functionality.
Naming is mostly consistent with verb_noun pattern (get_product, search_amazon_in), but price_history_link uses a noun_noun pattern. The deviation is minor and all names are clear.
Three tools is on the lower end but appropriate for a focused product info server. The set covers the essential operations: search, single product detail, and price history URL generation.
The tool surface covers the main workflows (search and detail fetch). A minor gap is that price_history_link only returns a URL rather than actual price history data, but the overall coverage is solid for the stated purpose.