Skip to main content
Glama

Search Amazon.in

search_amazon_in
Read-onlyIdempotent

Find amazon.in products by keyword and get ranked results with cheapest in-stock and best-value recommendations.

Instructions

Search amazon.in for products by keyword and return ranked listings.

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

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

Returns: JSON with schema: { "query": string, "total_results": number, // total listings parsed from the 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
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?

Discloses scraping nature, no API key needed, normalization, convenience picks with formulas, and detailed error handling (bot-check, network failures). Goes well beyond annotations (readOnly, idempotent). 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?

Front-loaded with purpose, then organized into args, returns, errors. Fairly concise but includes verbose formulas (best_value) and full return schema which could be shortened; still well-structured.

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?

Covers input validation, output schema (textual), error cases (bot-check, network), and convenience picks. No formal output schema but textual description is sufficient. Sibling tools noted in context but not in description; still complete for agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions. The description echoes parameters and adds return schema and business logic, but for parameter semantics specifically, it adds little beyond the schema (e.g., query: 'search keywords' already there).

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?

Clearly states verb 'Search' and resource 'amazon.in for products' with outcome 'ranked listings'. However, lacks explicit differentiation from sibling tools like get_product; an agent might not know when to switch.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives (e.g., get_product for specific products or price_history_link). Implied by purpose but not stated, leaving room for misuse.

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