Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_news_suggest

Use a partial query to fetch Yahoo News search-box autocomplete suggestions, returning a flat list of up to 20 news search terms.

Instructions

Yahoo News search autocomplete suggestions. Returns Yahoo News search-box autocomplete suggestions for the required partial query q, as a flat list of suggested news search terms in suggestions. count sets how many (default 10, clamped to 1 to 20). A query with no matches returns an empty array, not an error. The response also has query and fetched_at.

Input Schema

NameRequiredDescriptionDefault
qYesPartial search query to autocomplete
countNoNumber of suggestions to return, default 10, clamped to 1..20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers real behavioral context: empty array instead of an error on no match, count clamped to 1..20, and a flat list return. This meaningfully pre-empts agent confusion, though it lacks auth/rate-limit notes.

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?

Four tight sentences, all load-bearing, with the core purpose and required parameter front-loaded before the behavioral edge cases. Zero filler.

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 lookup tool with no output schema, the description covers the return shape (suggestions, query, fetched_at) and error behavior well. It stops short of usage guidance against alternatives, which is the only real 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 both parameters are already documented. The description restates the count default and clamp range but adds no syntax or format detail beyond the schema, so the baseline 3 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 ('Returns Yahoo News search-box autocomplete suggestions') and names the required input. An agent can immediately distinguish this from sibling search tools like yahoo_search_suggest or yahoo_news_home by the 'search-box autocomplete' scope.

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?

Usage is implied by the autocomplete framing, but the description never states when to reach for this tool versus, say, yahoo_search_suggest or a full news search, nor any prerequisite for the partial query. No exclusions or alternative routing are offered.

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