Channel3 Shopping

Browse Products

browse_products

Read-onlyIdempotent

Search and page through products for the storefront UI.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	One product type and its constraints in natural language (brand, color, material, size, price, gender). Good: "red leather jacket under $200"; "leather golf glove under $40". Bad: "gift ideas for dad"; "cool sneakers"; "golf glove or rangefinder".
`device_id`	No
`image_url`	No	Public image URL for visual search. Combine with `query` for text + image.
`thread_id`	No
`page_token`	No	Token from a previous response's next_page_token.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`products`	Yes
`next_page_token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 9, 2026
- removedOutput schema / properties / next_page_token / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / next_page_token / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Changed1 schema field changedAug 24, 2026
- addedInput schema / properties / device_id
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedAug 6, 2026
- addedInput schema / properties / thread_id
```
Added value: +{
+  "type": "string"
+}
```
First observedAug 5, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context such as pagination details, rate limits, or any caveats. It merely restates the action without enriching understanding of side effects or constraints.

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 a single, compact sentence with no wasted words. It is appropriately brief for a straightforward browsing tool. However, it lacks any structural organization or emphasis; it is merely a phrase without front-loading key distinguishing details.

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?

Given six parameters, zero required, and a rich set of siblings, the description is far too thin. It does not explain pagination usage, how to combine query and image_url, or any filtering nuances. An output schema exists, so return values are covered, but the overall usage context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, with descriptions for query, image_url, and page_token, but none for limit, device_id, or thread_id. The description mentions no parameters at all, so it does not compensate for the undocumented ones. An agent gets no help understanding what device_id or thread_id mean from the description.

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 and resource: 'Search and page through products'. It conveys the core action of browsing with pagination. However, it does not distinguish this tool from the sibling 'search_products' which likely overlaps, so it lacks sibling differentiation.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives like 'search_products' or 'get_products'. There are no exclusions, conditions, or hints about the appropriate context. The only context is 'for the storefront UI', which is a vague purpose indicator, not a usage guideline.

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

All Channel3 Shopping 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.