exNiche

Find retailer search links

find_retailers

Read-onlyIdempotent

Find which big retailers and brand stores to search for a product, with a ready-made search link for each. Use this when search_products returns nothing, when the shopper names a store or brand, or to give the shopper places to look. Returns up to 10 retailers (the brand's own store first, then category specialists, then general retailers), each with search_url, a short reason, and agent_access ('open' = you can fetch the page, 'blocks_bots' = hand the link to the shopper). No key needed. Example: {"query": "breville espresso machine", "region": "AU"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_retailers"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`query`	Yes	The product, e.g. 'wide fit hiking boots'. Leave out budget and size; they are stripped.
`region`	No	Shopper's country. Only retailers that serve it are returned. Coverage is deepest for AU.

Output Schema

Name	Required	Description	Default
`retailers`	No
`categories`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 11, 2026

changedInput schema / properties / query / description

Previous value: -"What the shopper wants, e.g. 'wide fit hiking boots'."New value: +"The product, e.g. 'wide fit hiking boots'. Leave out budget and size; they are stripped."

changedInput schema / properties / region / description

Previous value: -"Put retailers in this country first."New value: +"Shopper's country. Only retailers that serve it are returned. Coverage is deepest for AU."

AddedNov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint, openWorldHint, and idempotentHint annotations, the description discloses result ordering (brand store, then category specialists, then general retailers), the meaning of the agent_access values, and the instruction to hand blocks_bots links to the shopper rather than fetching them. It also notes that no key is needed. This is genuinely actionable behavioral context that the annotations alone do not provide.

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?

The description is front-loaded with the purpose, then the triggers, then the return shape, then a concrete example. Every sentence adds information, and the agent_access parenthetical is compact but clear.

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?

An output schema exists, so the description does not need to explain return values in full, but its summary of search_url, reason, and agent_access helps the agent act on the results. With three simple parameters and strong annotations, nothing an agent needs in order to call this correctly 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 67%, so the schema already documents query and region fairly well. The description still adds value with a concrete call example that shows the query/region pairing, and with the cap of 10 results, which relates to the limit parameter's maximum. It doesn't explain the limit default of 6 or how limit interacts with ordering, which is the remaining gap.

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 opens with a specific verb and resource: 'Find which big retailers and brand stores to search for a product, with a ready-made search link for each.' It also distinguishes itself from the sibling search_products by positioning itself as the fallback when that tool returns nothing.

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 gives three explicit triggering conditions: search_products returned nothing, the shopper named a store or brand, or the shopper needs places to look. The alternative, search_products, is named and its role relative to this tool is clear.

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

All exNiche 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?