Skip to main content
Glama
ncosic

logimu-shopping-mcp

by ncosic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search

Read-only

Filter through 17M+ Amazon and Walmart products by price, rating, reviews, BSR, and other criteria. Returns a sorted list of matching products with key details.

Instructions

Filtered query over the tracked-product warehouse (17M+ 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 or brand. 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 free lane 1 of 30 daily queries, capped at 25 rows. Keyed: 1 credit per 25 rows returned. Empty result sets are never billed.

Input Schema

TableJSON 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.
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). The free lane caps this at 25.
sellerNoRestrict to products this seller has been observed offering.
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.
categoryNoRestrict to a single product category.
price_maxNoMaximum current price, in the marketplace's local currency.
price_minNoMinimum current price, in the marketplace's local currency.
rating_minNoMinimum star rating, on a 0-5 scale.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv1.1.2
    • addedInput schema / properties / brand / description
      Added value: +"Exact brand name. Acts as the anchor when q is not given."
    • addedInput schema / properties / bsr_max
      Added value: +{
+  "description": "Maximum Best Sellers Rank. Use this to keep only strong sellers.",
+  "type": "integer"
+}
    • addedInput schema / properties / bsr_min
      Added value: +{
+  "description": "Minimum Best Sellers Rank. Lower BSR means stronger sales, so this excludes the best sellers.",
+  "type": "integer"
+}
    • addedInput schema / properties / category
      Added value: +{
+  "description": "Restrict to a single product category.",
+  "type": "string"
+}
    • addedInput schema / properties / fba
      Added value: +{
+  "description": "true = only Fulfilled by Amazon offers, false = only merchant-fulfilled. Omit to include both.",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / default
      Previous value: -25New value: +50
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return (up to 100). The free lane caps this at 25."
    • addedInput schema / properties / marketplace / description
      Added value: +"Which 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."
    • addedInput schema / properties / max_per_category
      Added value: +{
+  "description": "Cap how many results may come from any one category, to spread results across categories.",
+  "type": "integer"
+}
    • addedInput schema / properties / price_max / description
      Added value: +"Maximum current price, in the marketplace's local currency."
    • addedInput schema / properties / price_min / description
      Added value: +"Minimum current price, in the marketplace's local currency."
    • addedInput schema / properties / q / description
      Added value: +"Keyword 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."
    • addedInput schema / properties / rating_min / description
      Added value: +"Minimum star rating, on a 0-5 scale."
    • addedInput schema / properties / reviews_min / description
      Added value: +"Minimum number of reviews."
    • addedInput schema / properties / seller
      Added value: +{
+  "description": "Restrict to products this seller has been observed offering.",
+  "type": "string"
+}
    • addedInput schema / properties / sort / description
      Added value: +"Field to order results by. bsr sorts ascending (best sellers first); the others sort descending."
  2. First observedv1.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, but the description adds substantial context: cost limits (1 credit per 25 rows, 30 daily queries), anchor requirement (q or brand), coverage (BSR universe), and that empty results are not billed. No contradiction with annotations.

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

Conciseness5/5

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

The description is well-structured with sections (USE WHEN, DON'T USE, RETURNS, COVERAGE, COST) and is front-loaded with the main purpose. Every sentence adds essential information without redundancy.

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

Completeness4/5

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

Given the complexity (15 parameters, no output schema), the description covers the return fields, cost details, anchor requirement, and scope. It could mention pagination more explicitly, but overall it is quite complete for an agent to use correctly.

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?

Schema coverage is 100%, but the description adds value beyond schema by explaining anchor requirement, sort direction logic (bsr ascending, others descending), and literal keyword behavior for q. This enriches parameter understanding.

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 is a 'Filtered query over the tracked-product warehouse' and distinguishes from sibling tools (shopping, product) by specifying when not to use it. The verb 'query' and resource are explicit.

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?

The description provides explicit usage scenarios: 'USE WHEN the user wants a structured list matching explicit criteria' and contrasts with 'DON'T USE for best X buying advice (use shopping) or for a single known product (use product).' This gives clear when-to-use and alternatives.

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

Deploy Server

Other Tools