Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_search

Search Yahoo web results and get normalized data: title, URL, description, hostname, plus pagination. Resolves Yahoo redirect links to decoded destination URLs.

Instructions

Search Yahoo web results. Returns normalized Yahoo web search results for a query string: title, destination URL, description, and hostname, plus page-based pagination. Yahoo wraps every result link in its own click-tracking redirect; this endpoint always returns the decoded destination URL, never the raw redirect link. Results are fetched from Yahoo's own server-rendered search page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query
pageNo1-based page number, defaults to 1
time_rangeNoRestrict results by recency. Omit for unfiltered ('Anytime').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / time_range / enum
      Added value: +[
+  "day",
+  "week",
+  "month"
+]
  2. Changed1 schema field changedv1.14.0
    • addedInput schema / properties / time_range
      Added value: +{
+  "description": "Restrict results by recency. Omit for unfiltered ('Anytime').",
+  "type": "string"
+}
  3. Added

TDQS

A4.3/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 it delivers: it discloses normalization, that Yahoo's click-tracking redirect is always decoded, pagination behavior, and that results come from Yahoo's server-rendered page. It does not mention rate limits or error conditions, but for a read-only search tool this is strong disclosure.

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 sentences with no wasted words: purpose, returned fields, redirect behavior, and source. The critical gotcha about decoded URLs is front-loaded and the structure is easy to scan.

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?

For a 3-parameter search tool with no output schema, the description covers purpose, output fields, pagination, and a key behavioral caveat. The time_range semantics are already fully specified in the schema, so nothing an agent needs 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.

Parameters3/5

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

Schema coverage is 100%, so q, page, and time_range are already documented. The description adds only that pagination is page-based, which the schema's '1-based page number' already conveys. No meaningful parameter semantics are added beyond the schema.

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 Yahoo web results') and enumerates the returned fields (title, destination URL, description, hostname) plus pagination. The phrase 'web results' distinguishes it from sibling tools like yahoo_search_news, yahoo_search_images, and yahoo_search_local.

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?

The description clearly establishes the context: general Yahoo web search with normalized results and decoded URLs. It does not explicitly name alternatives or when-not conditions, but the 'web results' scope and the distinct sibling names make the intended use evident.

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