Skip to main content
Glama

Search Amazon.in

search_amazon_in
Read-onlyIdempotent

Search Amazon India for products by keyword and get ranked results including cheapest in-stock and best-value picks.

Instructions

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:

  • cheapest_in_stock: lowest price among listings showing stock

  • best_value: weighted score = rating × log10(reviews+10) / sqrt(price), requires >=10 reviews

Args:

  • query (string, 2-200 chars): search keywords

  • max_results (int, 1-20, default 5): number of listings to return

  • page (int, 1-20, default 1): which result page to fetch; use to look past page 1

  • include_sponsored (bool, default false): include ad listings

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:

  • "Amazon served a bot-check page" → wait 30-60s and retry

  • "Failed to reach amazon.in" → transient network or throttling

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page to fetch (1-based). Amazon shows ~16-24 organic listings per page; use this to look past the first page. Default 1.
queryYesKeyword search query (e.g., 'bluetooth speaker under 2000')
max_resultsNoMaximum listings to return (1-20). Default 5.
include_sponsoredNoInclude sponsored / ad listings. Defaults to false.
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds that it scrapes the public search page (no API key), error handling details, and the computation of convenience picks (cheapest_in_stock, best_value) with formulas. No contradictions.

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?

Well-structured with clear sections: purpose, usage guidelines, internal details, args, output schema, error handling. Front-loaded with purpose and usage. Slightly lengthy but each part is justified. Could be more concise by moving output schema to a separate field.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Thorough description covering all aspects: purpose, usage, parameter details, output structure, error handling, convenience picks. No output schema field exists, but the description provides full JSON schema. Appropriate for a search tool with pagination and computed fields.

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?

Input schema covers 100% of parameters with descriptions. The description adds context like query length limits, page usage explanation, and the two computed fields (cheapest_in_stock, best_value) which are derived but not parameters. Baseline is 3; this adds extra value.

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?

The description clearly states it searches Amazon India for products by keyword and returns ranked listings. It distinguishes from sibling tools 'get_product' and 'price_history_link' by focusing on general search. The verb 'search' and resource 'amazon.in' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says 'Use this by default' for various shopping intents and gives example phrasings. It also states preference over web search and that the user need not name the MCP. This is comprehensive guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/justadityaraj/amazon-in-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server