Skip to main content
Glama

amazon_search

Search Amazon by query and retrieve product listings with prices, ratings, ASINs, and sponsored status. Supports pagination and multiple country domains.

Instructions

Retrieves search result listings from Amazon for any query, including product titles, prices, ratings, review counts, sponsored status, and ASINs, plus pagination links. [Credits: 1 API credit per successful request when country=us (5 credits for other countries per the country parameter). premium=true costs an additional 25 credits per request.] Notes: Pagination is via the page parameter (starts at 1); the response also returns a pagination array of ready-to-use next-page Amazon URLs (informational, not directly usable as this API's own next-page param). Returns: { search_message, location, results: [{type, title, image, has_prime, is_best_seller, is_amazon_choice, limited_time_deal, deal_of_the_day, stars, total_reviews, optimized_url, sponsored, number_of_people_bought, asin, availability_quantity, price_string, price_symbol, price, extracted_price, currency, climate_pledge_friendly, absolute_position, organic_position, certification}], pagination: [urls] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesThe page number of results to retrieve. Starts at 1.
queryYesThe search query string to look up on Amazon.
domainYesTLD extension of the Amazon domain. Examples: com, in, de, fr, co.uk. See Amazon Supported TLDs doc for the full list.
countryYesISO country code for targeting a specific Amazon marketplace. Costs 5 credits per request except USA which costs 1 credit. See Amazon Supported Countries doc for the full list. (default: us)
premiumNoSet to true to use premium proxies for scraping Amazon, which increases the chances of retrieving sponsored results. Costs 25 credits per request. (default: false)
languageNoStandard ISO 639-1 language code (e.g. en, de, fr) to specify the language for product data.
postal_codeNoTo get data from a particular postal code.
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses credit costs per country and premium, and explains pagination behavior (page parameter and informational pagination array). It does not mention rate limits, error handling, or side effects, but for a read-only search tool, these are less critical.

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?

The description is well-structured with a clear main sentence, credit details in brackets, pagination note, and return format. It is slightly verbose but front-loaded with the primary purpose, making it effective.

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?

With no output schema, the description thoroughly details the return structure with example fields. It covers all necessary aspects of the tool's functionality, including multiple parameters and their effects, making it complete for an agent to use.

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

Parameters5/5

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

Schema coverage is 100%, with each parameter documented. The description adds value beyond the schema by explaining credit cost implications for country and premium, and clarifying that the page parameter starts at 1 and the pagination array is informational.

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 the tool retrieves search result listings from Amazon for any query, listing specific data points (titles, prices, ratings, etc.) and pagination links. It distinguishes itself from sibling tools like amazon_product, amazon_reviews, etc., which focus on single product details or reviews.

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

Usage Guidelines3/5

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

The description includes credit costs and pagination notes but does not explicitly state when to use this tool versus alternatives. The context of sibling tools implies usage, but the description lacks direct guidance on scenarios or exclusions.

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/alessandrobenigni/ScrapingDog-MCP'

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