Crawlora MCP

yahoo_shopping_suggest

Read-only

Yahoo Shopping search-box autocomplete suggestions for a partial query. This is typeahead only; Yahoo Shopping exposes no working product-results or filter endpoint.

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": {
      "q": "<q>"
    },
    "name": "yahoo_shopping_suggest"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Partial search query
`count`	No	Upstream suggestion count; omitted defaults to 10, zero/negative values preserve Yahoo's empty-result behavior, and values above 20 are capped

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuine scope context by flagging the upstream endpoint limitation. It does not discuss rate limiting or result shape, but with an output schema present that omission is minor.

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, no waste, with the positive definition front-loaded and the limitation immediately after. Every clause earns its place.

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?

Output schema, annotations, and both parameters are documented elsewhere, and the description supplies the one thing those fields cannot: that this is typeahead-only with no product endpoint. Only a minor gap remains around result locality/language behavior.

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 coverage is 100% and the schema itself documents the interesting behavior (default 10, zero/negative preserving empty results, >20 capped). The description adds nothing about `q` or `count`, so the baseline 3 for fully-documented params applies.

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 and resource ('search-box autocomplete suggestions for a partial query') and immediately scopes it against the broader Yahoo Shopping family by declaring there is no working product-results or filter endpoint. An agent can tell instantly that this is typeahead, not a product search.

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?

Explicitly states the when-not: do not expect product results or filters from Yahoo Shopping, so an agent won't waste calls hunting for them. It does not name concrete alternate siblings (e.g., yahoo_search, yahoo_shopping_category) for an agent that actually wants products, which keeps it short of a 5.

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

All Crawlora MCP 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.