logimu-shopping-mcp

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 free lane 1 of 30 daily queries, capped at 25 rows. Keyed: 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

TableJSON Schema

Name	Required	Description	Default
`q`	No	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.
`fba`	No	true = only Fulfilled by Amazon offers, false = only merchant-fulfilled. Omit to include both.
`fbm`	No	Only merchant-fulfilled listings. The counterpart of fba, which was already exposed.
`sort`	No	Field to order results by. bsr sorts ascending (best sellers first); the others sort descending.	bsr
`brand`	No	Exact brand name. Acts as the anchor when q is not given.
`limit`	No	Maximum rows to return (up to 100). The free lane caps this at 25.
`seller`	No	Restrict 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_max`	No	Maximum Best Sellers Rank. Use this to keep only strong sellers.
`bsr_min`	No	Minimum Best Sellers Rank. Lower BSR means stronger sales, so this excludes the best sellers.
`category`	No	A 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_max`	No	Maximum current price, in the marketplace's local currency.
`price_min`	No	Minimum current price, in the marketplace's local currency.
`rating_max`	No	Maximum average star rating. USE WHEN looking for products whose reviews are weak — an incumbent rated 3.2 is an opening.
`rating_min`	No	Minimum star rating, on a 0-5 scale.
`fulfillment`	No	Buy-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.
`marketplace`	No	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.	amazon-us
`reviews_min`	No	Minimum number of reviews.
`max_per_category`	No	Cap how many results may come from any one category, to spread results across categories.
`seller_count_max`	No	Maximum 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_min`	No	Minimum 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.

Changed1 schema field changedSep 17, 2026

addedInput schema / properties / fulfillment

Added value: +{
+  "description": "Buy-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.",
+  "enum": [
+    "amz",
+    "fba",
+    "fbm"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedAug 10, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "q"
-    ]
-  },
-  {
-    "required": [
-      "brand"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "q"
+    ]
+  },
+  {
+    "required": [
+      "brand"
+    ]
+  },
+  {
+    "required": [
+      "category"
+    ]
+  }
+]

changedInput schema / properties / category / description

Previous value: -"Restrict to a single product category. REFINEMENT ONLY - cannot be used on its own; pair it with q or brand, which are the only anchors. To browse a category with no keyword, use the shopping tool instead."New value: +"A 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."

changedInput schema / properties / seller / description

Previous value: -"Restrict to products this seller has been observed offering. REFINEMENT ONLY - cannot be used on its own; pair it with q or brand, which are the only anchors."New value: +"Restrict 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)."

Changed5 schema fields changedAug 6, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "q"
+    ]
+  },
+  {
+    "required": [
+      "brand"
+    ]
+  }
+]

addedInput schema / properties / fbm

Added value: +{
+  "description": "Only merchant-fulfilled listings. The counterpart of fba, which was already exposed.",
+  "type": "boolean"
+}

addedInput schema / properties / rating_max

Added value: +{
+  "description": "Maximum average star rating. USE WHEN looking for products whose reviews are weak — an incumbent rated 3.2 is an opening.",
+  "type": "number"
+}

addedInput schema / properties / seller_count_max

Added value: +{
+  "description": "Maximum 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.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / seller_count_min

Added value: +{
+  "description": "Minimum number of sellers competing on the listing. USE WHEN the user wants proven demand rather than an untested listing.",
+  "minimum": 0,
+  "type": "integer"
+}

Changed2 schema fields changedAug 5, 2026

changedInput schema / properties / category / description

Previous value: -"Restrict to a single product category."New value: +"Restrict to a single product category. REFINEMENT ONLY - cannot be used on its own; pair it with q or brand, which are the only anchors. To browse a category with no keyword, use the shopping tool instead."

changedInput schema / properties / seller / description

Previous value: -"Restrict to products this seller has been observed offering."New value: +"Restrict to products this seller has been observed offering. REFINEMENT ONLY - cannot be used on its own; pair it with q or brand, which are the only anchors."

Changed1 schema field changedAug 4, 2026

changedInput schema / properties / marketplace / enum

Previous value: -[
-  "amazon-us",
-  "amazon-uk",
-  "amazon-de",
-  "amazon-ca",
-  "amazon-au",
-  "walmart"
-]New value: +[
+  "amazon-us",
+  "amazon-uk",
+  "amazon-de",
+  "amazon-ca",
+  "amazon-au",
+  "amazon-fr",
+  "amazon-it",
+  "amazon-es",
+  "amazon-jp",
+  "amazon-mx",
+  "amazon-br",
+  "walmart"
+]

Changed1 schema field changedJul 30, 2026

changedInput schema / properties / q / description

Previous value: -"Keyword matched against the product title. Acts as the anchor when brand is not given."New 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."

Changed1 schema field changedJul 29, 2026

changedInput schema / properties / marketplace / description

Previous value: -"Which tracked marketplace to query."New 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."

Changed15 schema fields changedJul 29, 2026

changedInput schema / properties / brand / description

Previous value: -"exact brand. An anchor."New value: +"Exact brand name. Acts as the anchor when q is not given."

addedInput schema / properties / bsr_max / description

Added value: +"Maximum Best Sellers Rank. Use this to keep only strong sellers."

addedInput schema / properties / bsr_min / description

Added value: +"Minimum Best Sellers Rank. Lower BSR means stronger sales, so this excludes the best sellers."

addedInput schema / properties / category / description

Added value: +"Restrict to a single product category."

addedInput schema / properties / fba / description

Added value: +"true = only Fulfilled by Amazon offers, false = only merchant-fulfilled. Omit to include both."

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."
```

addedInput schema / properties / max_per_category / description

Added value: +"Cap how many results may come from any one category, to spread results across categories."

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."

changedInput schema / properties / q / description

Previous value: -"keyword (title). An anchor."New value: +"Keyword matched against the product title. Acts as the anchor when brand is not given."

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 / description

Added value: +"Restrict to products this seller has been observed offering."

addedInput schema / properties / sort / description

Added value: +"Field to order results by. bsr sorts ascending (best sellers first); the others sort descending."

First observedJul 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context: return fields (product_id, product_url, etc.), ordering semantics, coverage limits ('not the entire Amazon catalog'), cost structure ('free lane 1 of 30 daily queries', '1 credit per 25 rows'), and a dated seller-feedback note about an extra seller_ratings array. 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.

Conciseness4/5

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

The description is long but deliberately structured with labeled sections (COVERAGE, COST, SELLER FEEDBACK) and front-loaded purpose and usage. Every sentence adds value—even the seller-feedback note clarifies an evolving response shape. It is dense but appropriate for a tool with 20 parameters; a slightly shorter version might be possible, but nothing is fluff.

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 20-parameter tool with no output schema, the description is remarkably complete: it lists return fields, covers anchor semantics, marketplace selection, cost/limits, coverage scope, and even the optional seller_ratings array. An agent has everything needed to call it correctly, including the caution about empty result sets not being billed.

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%, so baseline is 3, but the description goes well beyond the schema: it explains that q is literal not semantic, category can act as anchor or refinement, seller_count_max is 'the core sourcing filter' for low competition, and rating_max is for weak-review incumbents. This adds decision-relevant meaning to parameters that the schema alone does not convey.

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 states a specific verb ('query') and a specific resource ('tracked-product warehouse'), and explicitly differentiates from siblings: 'DON'T USE for "best X" buying advice (use shopping, which ranks and groups), or for a single known product (use product).' It also gives concrete example queries, making the tool's purpose unmistakable.

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 provides explicit USE WHEN and DON'T USE conditions, names the alternative tools (shopping and product), and specifies an anchor requirement ('Requires an anchor: pass q, brand, or category'). This leaves no ambiguity about when to invoke this tool versus its siblings.

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

All logimu-shopping-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?