Skip to main content
Glama
BACH-AI-Tools

Real Time Amazon Data MCP Server

product_search

Search Amazon products and offers with pagination, sorting, price ranges, brand/category filters, and product condition options to find exactly what you need.

Instructions

Search for products \u0026 offers on Amazon with pagination support and multiple filters and options such as sort option, price range, product condition filter, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResults page to return. Default: 11
brandNoFind products with a specific brand. Multiple brands can be specified as a comma (,) separated list. The brand values can be seen from Amazon's search left filters panel, as seen here. Examples: SAMSUNG Google,Apple
queryYesSearch query (supports both free-form text queries or a product asin).
fieldsNoA comma separated list of product fields to include in the response (field projection). By default all fields are returned. Example: product_price,product_url,is_best_seller,sales_volume
countryNoSets the Amazon domain, marketplace country, language and currency. Default: US Allowed values: US, AU, BR, CA, CN, FR, DE, IN, IT, MX, NL, SG, ES, TR, AE, GB, JP, SA, PL, SE, BE, EG
sort_byNoReturn the results in a specific sort order. Default: RELEVANCE Allowed values: RELEVANCE, LOWEST_PRICE, HIGHEST_PRICE, REVIEWS, NEWEST, BEST_SELLERS
categoryNoFilter by specific numeric Amazon category. The category ID can be obtained from the Amazon category results URL, for example: https://amazon.com/s?node=2858778013 - the Amazon Category ID is 2858778013. Multiple category values can be separated by comma (e.g. categoryId1,categoryId2).
is_primeNoExample value:
languageNoThe language of the results. In case not specified, results will be returned in the default domain language. Supported languages per country: US: en_US, es_US AU: en_AU BR: pt_BR CA: en_CA, fr_CA FR: fr_FR, en_GB DE: de_DE, en_GB, cs_CZ, nl_NL, pl_PL, tr_TR, da_DK IN: en_IN, hi_IN, ta_IN, te_IN, kn_IN, ml_IN, bn_IN, mr_IN IT: it_IT, en_GB MX: es_MX NL: nl_NL, en_GB SG: en_SG ES: es_ES, pt_PT, en_GB TR: tr_TR AE: en_AE, ar_AE GB: en_GB JP: ja_JP, en_US, zh_CN SA: ar_AE, en_AE PL: pl_PL SE: sv_SE,
max_priceNoOnly return product offers with price lower than a certain value. Specified in the currency of the selected country. For example, in case country=US, a value of 105.34 means $105.34.0
min_priceNoOnly return product offers with price greater than a certain value. Specified in the currency of the selected country. For example, in case country=US, a value of 105.34 means $105.34.0
seller_idNoFind products sold by specific seller (merchant). Multiple sellers can be specified as a comma (,) separated list. Examples: A02211013Q5HP3OMSZC7W AM7YCCDZROLB2,A1D09S7Q0OD6TH
category_idNoFind products in a specific category / department (e.g. computers-intl-ship). Use the Product Category List endpoint to get a list of valid categories and their ids for the country specified in the request. For numeric Amazon category IDs, use the category parameter instead. Default: aps (All Departments)
four_stars_and_upNoExample value:
product_conditionNoReturn products in a specific condition. Default: ALL Allowed values: ALL, NEW, USED, RENEWED, COLLECTIBLE
additional_filtersNoAny filters available on the Amazon page but not part of this endpoint's parameters. The filter values can be extracted from the rh parameter in the Amazon search URL after applying the filter of interest on the Amazon search results page. Multiple filters are supported and can be separated by comma (,). For example, when searching for science books with the Paperback book format filter selected, the Amazon URL is: https://www.amazon.com/s?k=science+books&rh=p_n_feature_browse-bin%3A2656022011 a
deals_and_discountsNoReturn deals and discounts in a specific condition. Default: NONE Allowed values: NONE, ALL_DISCOUNTS, TODAYS_DEALS
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It mentions pagination support and filter options but doesn't disclose rate limits, auth requirements, result volume/cap, what happens when no results, or the meaning of minimal default text parameters like is_prime and four_stars_and_up which are empty in the schema. Search execution behavior beyond 'returns results' is undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single reasonably compact sentence that covers the tool's headline features efficiently. However, it omits helpful guidance and front-loads capabilities that the schema already documents, leaving the sentence informative but not optimally structured for an agent deciding whether to use this tool.

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

Completeness2/5

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

Despite 17 parameters and no output schema, the description offers minimal context beyond naming capabilities. It doesn't discuss the default country/currency behavior, that query supports ASINs (though schema notes this), pagination behavior/cap, or the relationships to closely related sibling tools like product_offers and deals. For a high-complexity tool, this is under-specified.

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%, so the baseline is 3. The description itself adds no parameter meaning beyond what the schema provides, and it even references capabilities (sort, price range) that are already fully documented per-parameter in the schema. The description does not add value beyond the schema's own documentation.

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?

The description states a clear verb+resource ('Search for products & offers on Amazon') and lists capabilities (pagination, sort, price range, condition filter). However, it doesn't distinguish from siblings like product_offers, product_details, or products_by_category, which are related but different scopes. The purpose is clear but sibling differentiation is absent.

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 implies usage for product searching with various filters but doesn't explicitly say when to use this over siblings like products_by_category or product_offers. The scope of this tool vs the more specific sibling tools is implied but never stated, so an agent may struggle to decide which to invoke for a given query.

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/BACH-AI-Tools/bach-real_time_amazon_data'

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