Feedico: coupons, deals & products

Search products

search_products

Read-only

Search millions of products from affiliate feeds by keyword, brand, store or exact SKU / part number, with price filters. Returns price, sale price, store, image and a tracked product link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_products"
  }
}

Input Schema

Name	Required	Description
`sku`	No	Exact SKU / manufacturer part number
`brand`	No	Product brand / manufacturer, e.g. "Anker"
`limit`	No	How many results (default 8)
`query`	No	What the user is looking for, e.g. "running shoes"
`store`	No	Limit to one store, e.g. "DHgate"
`onSale`	No	Only discounted products
`maxPrice`	No	Highest price, in the product currency
`minPrice`	No	Lowest price, in the product currency
`countries`	No	ISO country codes to limit offers to, e.g. ["US"] or ["GB","IE"]

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 22, 2026
- addedInput schema / properties / brand / description
```
Added value: +"Product brand / manufacturer, e.g. \"Anker\""
```
- addedInput schema / properties / maxPrice / description
```
Added value: +"Highest price, in the product currency"
```
- addedInput schema / properties / minPrice / description
```
Added value: +"Lowest price, in the product currency"
```
First observedOct 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint; the description adds genuinely non-obvious context on top: results come from external affiliate feeds and each result carries a *tracked* affiliate link. That tracking disclosure is materially useful for an agent reporting links to a user. It stops short of describing ranking, pagination behavior, or empty-result semantics.

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?

Two sentences, zero filler. The searchable dimensions are front-loaded and the return payload is summarized at the end, matching the order an agent needs to make a decision.

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?

Strong for a read-only search tool: since there is no output schema, the description's return-field list (price, sale price, store, image, tracked link) is exactly the compensation needed. Minor gap: nothing on result ordering, the default limit of 8, or behavior when no matches are found.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in the schema; baseline 3 applies. The description reinforces keyword/brand/store/SKU and price filtering but adds no syntax, currency, or combination rules beyond the schema, and omits onSale and countries entirely.

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?

States a specific verb (search) and resource (products from affiliate feeds) and enumerates the match dimensions: keyword, brand, store, exact SKU/part number, plus price filters. The resource distinction from siblings (search_stores, search_coupons, get_store_link) is self-evident from the text, so an agent can route correctly without opening a schema.

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

Usage Guidelines3/5

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

The description implies *how* to query by listing match modes (keyword vs exact SKU) and mentions price filters, which hints at the right parameters. But it never states when to prefer this over search_stores/search_coupons, nor any exclusions or prerequisites — usage is inferred rather than spelled out.

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

All Feedico: coupons, deals & products 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?