Channel3 Product Search
Server Details
Product search and price comparison for AI agents. Search 100M+ products across thousands of retailers by text or image, compare live offers and prices, and turn any merchant URL into structured product data. No API key required to start; add one for unlimited use and affiliate commission.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.9/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The single search tool has a unique and clear purpose.
The single tool is named 'search', which is a straightforward verb that matches its function. With only one tool, naming consistency is inherently maintained.
A single tool for product search feels minimal but can be acceptable if the search tool returns comprehensive results. Typically, more tools (e.g., for details, categories) would be expected, but the count is not unreasonable for a focused utility.
The server offers only a search tool, lacking operations like getting product details, filtering, or managing a product list. While the search is thorough, the tool surface has significant gaps for a full product search domain.
Available Tools
1 toolsearchProduct SearchARead-onlyInspect
Search a catalog of millions of products and brands. Returns matching products with title, brand, images, and offers from different retailers. Each offer has a price and a buy URL. Present multiple offers so the user can compare prices and choose where to buy.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Free-text search query, or a product URL to look up. You can include brand names, product types, attributes, colors, etc. | |
| brands | No | Brand names to filter by (e.g. ["Nike", "Adidas"]). | |
| gender | No | Filter by intended gender. | |
| websites | No | Domains to filter by (e.g. ["nike.com"]). | |
| image_url | No | Public image URL to find visually similar products. | |
| max_price | No | Maximum price in USD (inclusive), in dollars and cents. | |
| min_price | No | Minimum price in USD (inclusive), in dollars and cents. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, confirming safety. The description adds that results include offers with prices and buy URLs, and suggests presenting multiple options, which is helpful context beyond the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with three sentences, front-loading the core search capability. It is well-structured but could be slightly more streamlined.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description explains the return content (title, brand, images, offers) and usage guidance, which compensates for the lack of an output schema. For a search tool with 7 parameters, it provides sufficient context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All 7 parameters have schema descriptions, achieving 100% coverage. The tool description does not add further parameter details beyond what the schema already provides, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches millions of products and brands, and specifies what is returned (title, brand, images, offers with price and buy URL). It uses a specific verb 'search' and describes the resource comprehensively.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description advises to present multiple offers for comparison, which is a usage guideline. However, it does not provide explicit when-to-use or when-not-to-use instructions, nor alternatives since no siblings exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!