Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_shopping_suggest

Yahoo Shopping autocomplete suggestions. Returns suggestions from the typeahead endpoint used by Yahoo Shopping's search box.

Instructions

Yahoo Shopping autocomplete suggestions. Returns suggestions from the typeahead endpoint used by Yahoo Shopping's search box. Yahoo does not expose a working Shopping product-results grid or product filters; this route provides autocomplete only.

Input Schema

NameRequiredDescriptionDefault
qYesPartial search query
countNoUpstream suggestion count; omitted defaults to 10, zero/negative values preserve Yahoo's empty-result behavior, and values above 20 are capped

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does carry useful context: it identifies the upstream typeahead endpoint and discloses a real capability limitation (no product grid or filters). However, it says nothing about return shape, suggestion object fields, or rate/limit behavior of the upstream call.

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?

Three short sentences, front-loaded with the purpose, then the source, then the constraint. Minor redundancy between 'autocomplete suggestions' and 'provides autocomplete only', but nothing is wasted.

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?

For a two-parameter read-only suggestion endpoint with a fully described schema and no output schema, the description gives enough to call it correctly and to know what it will not return. Only the shape of returned suggestions is left unstated, which is a small gap.

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 the 'q' and 'count' semantics (default 10, non-positive preserved, cap at 20) are already fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 first sentence names a specific verb and resource (autocomplete suggestions for Yahoo Shopping) and the third narrows the scope to the typeahead endpoint. It is clearly differentiable from siblings such as yahoo_shopping_categories or yahoo_shopping_store, though it never explicitly names an alternative for 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 Guidelines3/5

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

The description implies usage (typeahead expansion of partial queries) and gives a useful exclusion – there is no working product-results grid or filter route – but it never states when to pick this over the many other yahoo_shopping_* tools or what query patterns it suits.

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

Deploy Server

Other Tools