mcp-gateway

search_products_enriched

Read-onlyIdempotent

Search products with enriched data including structured attributes, variants, GTIN, and images. Ideal for comparison and detailed product discovery. Matching is keyword/substring-based (title, description, tags, vendor) with rating-then-review ordering — the rating and review count it orders by are asserted by the merchant and are not verified by Trusteed. Use this when you have concrete keywords, a category, or a price range.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (1-20)
`query`	Yes	Search query
`category`	No	Filter by category
`max_price`	No	Maximum price
`min_price`	No	Minimum price

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`total`	Yes
`products`	Yes
`_carousel`	No
`sort_provenance_warning`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

addedOutput schema / properties / _carousel

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "apiEndpoint": {
+      "type": "string"
+    },
+    "initialCategory": {
+      "type": "string"
+    },
+    "productsForArtifact": {
+      "items": {},
+      "type": "array"
+    },
+    "storeSlug": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "apiEndpoint",
+    "storeSlug",
+    "productsForArtifact",
+    "initialCategory"
+  ],
+  "type": "object"
+}

Changed7 schema fields changedSep 17, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / products / items / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / products / items / properties / attributes / items / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / products / items / properties / images / items / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / products / items / properties / rating_provenance / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "note": {
-        "type": "string"
-      },
-      "origin": {
-        "const": "merchant",
-        "type": "string"
-      },
-      "strength": {
-        "const": "claimed",
-        "type": "string"
-      },
-      "verified": {
-        "const": false,
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "origin",
-      "strength",
-      "verified",
-      "note"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "note": {
+        "type": "string"
+      },
+      "origin": {
+        "const": "merchant",
+        "type": "string"
+      },
+      "strength": {
+        "const": "claimed",
+        "type": "string"
+      },
+      "verified": {
+        "const": false,
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "origin",
+      "strength",
+      "verified",
+      "note"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / products / items / properties / variants / items / additionalProperties
```
Previous value: -falseNew value: +true
```

AddedSep 9, 2026
RemovedSep 1, 2026

Changed4 schema fields changedAug 24, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties

Added value: +{
+  "category": {
+    "description": "Filter by category",
+    "type": "string"
+  },
+  "limit": {
+    "default": 10,
+    "description": "Max results (1-20)",
+    "maximum": 20,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "max_price": {
+    "description": "Maximum price",
+    "type": "number"
+  },
+  "min_price": {
+    "description": "Minimum price",
+    "type": "number"
+  },
+  "query": {
+    "description": "Search query",
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[
+  "query"
+]
```

AddedJul 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the readOnly/idempotent annotations: matching is keyword/substring-based on specific fields, ordering is rating-then-review, and crucially it warns that ratings/review counts are merchant-asserted and not verified by Trusteed. This is meaningful, honest behavioral disclosure.

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?

Three sentences, each earning its place: the enriched-data scope, the matching/ordering behavior with the trust caveat, and the when-to-use guidance. It is front-loaded with the primary purpose and contains no filler.

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 an output schema present and annotations covering safety semantics, the description sufficiently covers what an agent needs to select and call this tool: result richness, search behavior, ordering caveat, and input context. No critical operational behavior is missing.

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 description coverage is 100%, so the baseline is 3. The description adds value by clarifying what the query parameter actually does ('keyword/substring-based (title, description, tags, vendor)') and reinforcing the intended use of category and price-range filters. It does not describe every parameter but adds meaning beyond the schema.

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 and resource ('Search products') and clearly differentiates this tool by its enriched result data: 'structured attributes, variants, GTIN, and images.' It also states the intended use ('comparison and detailed product discovery'), making its purpose distinct from the simpler sibling search_products.

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

Usage Guidelines4/5

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

It gives explicit guidance on when to use the tool: 'Use this when you have concrete keywords, a category, or a price range.' It does not explicitly name alternatives or exclusion cases, so it stops short of the fullest when/when-not guidance, but the context is clear.

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

All mcp-gateway 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?