Skip to main content
Glama

search

Read-onlyIdempotent

Filtered query over the tracked-product warehouse (24M+ Amazon and Walmart products). USE WHEN the user wants a structured list matching explicit criteria: 'well-rated dehumidifiers under $150 with 1000+ reviews', 'everything by brand X sorted by BSR', 'FBA products in this category'. DON'T USE for 'best X' buying advice (use shopping, which ranks and groups), or for a single known product (use product). RETURNS a flat list of matching products with product_id (the ASIN on Amazon, the numeric item ID on Walmart), product_url, title, brand, price, rating, review count, BSR, seller count and marketplace, ordered by the sort field. Requires an anchor: pass q, brand, or category. Cite product_id when the user may want to act on a specific row, and pass it to the product tool for that item's full history. Every response row is observed marketplace data (the marketplace field names it). COVERAGE the continuously tracked BSR product universe, not the entire Amazon catalog. COST paid plans only (sign in or an API key; the no-signup lane has the shopping tool only). 1 credit per 25 rows returned. Empty result sets are never billed. SELLER FEEDBACK (2026-09-18): the response also carries seller_ratings - a separate array with seller_positive_pct, seller_feedback_count, seller_rating and observed_at for every buy-box seller named in the rows (Amazon marketplaces; absent on Walmart). Row shapes are unchanged. Not billed.

Input Schema

NameRequiredDescriptionDefault
qNoKeyword matched against the product title. Acts as the anchor when brand is not given. Literal keywords, not semantic: every term must match, so extra or inferred words only narrow the result set. Query in the marketplace's own language — there is no translation.
fbaNotrue = only Fulfilled by Amazon offers, false = only merchant-fulfilled. Omit to include both.
fbmNoOnly merchant-fulfilled listings. The counterpart of fba, which was already exposed.
sortNoField to order results by. bsr sorts ascending (best sellers first); the others sort descending.bsr
brandNoExact brand name. Acts as the anchor when q is not given.
limitNoMaximum rows to return (up to 100).
sellerNoRestrict to products this seller has been observed offering. REFINEMENT ONLY - cannot be used on its own; pair it with an anchor (q, brand, or category).
bsr_maxNoMaximum Best Sellers Rank. Use this to keep only strong sellers.
bsr_minNoMinimum Best Sellers Rank. Lower BSR means stronger sales, so this excludes the best sellers.
categoryNoA department or sub-category name (e.g. 'Home & Kitchen', 'Beading Storage'), matched in full and case-insensitively against the product's category chain — comma-separate several. Works BOTH ways: as an ANCHOR on its own to browse a category with no keyword ('everything in Home & Kitchen under $30, most reviews first'), or as a REFINEMENT alongside q or brand. A category-only browse returns the category's top products by in-category best-seller rank, then applies your filters and sort.
price_maxNoMaximum current price, in the marketplace's local currency.
price_minNoMinimum current price, in the marketplace's local currency.
rating_maxNoMaximum average star rating. USE WHEN looking for products whose reviews are weak — an incumbent rated 3.2 is an opening.
rating_minNoMinimum star rating, on a 0-5 scale.
fulfillmentNoBuy-box fulfilment of the listing: amz = sold by Amazon itself, fba = a third party fulfilled by Amazon, fbm = merchant-fulfilled. Finer than fba/fbm because it separates Amazon Retail from FBA sellers. Amazon marketplaces only.
marketplaceNoWhich tracked marketplace to query. walmart = Walmart US (United States only). Pick the marketplace matching the user's country or locale when known; default amazon-us.amazon-us
reviews_minNoMinimum number of reviews.
max_per_categoryNoCap how many results may come from any one category, to spread results across categories.
seller_count_maxNoMaximum number of sellers competing on the listing. USE WHEN the user asks for products with little competition, few sellers, or an easy listing to win — this is the core sourcing filter.
seller_count_minNoMinimum number of sellers competing on the listing. USE WHEN the user wants proven demand rather than an untested listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum rows to return (up to 100). The free lane caps this at 25."New value: +"Maximum rows to return (up to 100)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond that: paid-plan requirement, credit cost per 25 rows, no billing for empty results, marketplace coverage limits, anchor requirement, and the separate seller_ratings array. These details materially help an agent decide whether and how to invoke the tool.

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 dense but justified for a 20-parameter tool, and it front-loads purpose, use cases, and exclusions. The seller-feedback changelog note and repeated cost/coverage details add some length, but overall the structure is clear and mostly earns its space.

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?

For a complex search tool with no output schema, the description explains the returned row shape, product_id meaning, seller_ratings behavior, marketplace coverage, billing rules, and anchor requirement. An agent has enough context to invoke it correctly without needing undocumented assumptions.

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 description coverage is 100%, and the schema itself documents all 20 parameters in detail, including anyOf anchor constraints, enums, defaults, and ranges. The description reinforces the anchor rule and gives example filter combinations, but adds little parameter meaning beyond the schema, so the baseline 3 is appropriate.

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 gives a specific verb and resource: 'Filtered query over the tracked-product warehouse (24M+ Amazon and Walmart products).' It clearly distinguishes the tool from siblings by naming shopping for buying advice and product for a single known product.

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?

It explicitly states when to use the tool with concrete example queries and when not to use it, naming the better alternatives: shopping for 'best X' advice and product for a single known item. It also states the anchor requirement and points to product for full item history.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.