Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_search

Search Yahoo web results by query to retrieve titles, decoded destination URLs, descriptions, hostnames, and paginated pages, with optional recency filters for day, week, or month.

Instructions

Search Yahoo web results. Returns 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.

Input 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/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 a genuinely non-obvious behavioral fact: Yahoo wraps links in click-tracking redirects, and this endpoint always returns the decoded destination URL. That is exactly the kind of quirk that prevents downstream mistakes. It still omits auth/rate-limit/error behavior, so it is strong but not complete.

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?

Three sentences, front-loaded with purpose and output shape, then the link-decoding caveat. Every sentence carries information; nothing is redundant.

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?

No output schema exists, so the description usefully lists the returned fields and pagination, and it flags the redirect-decoding behavior. It stops short of covering per-page result counts, auth needs, or failure modes, leaving a small gap for a search endpoint.

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 schema already documents q, page, and time_range fully; the description only echoes page-based pagination and adds no syntax or semantics beyond the schema. 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 ("Search Yahoo web results") and enumerates the returned fields (title, destination URL, description, hostname). The "web results" scope implicitly differentiates it from the yahoo_search_images/news/videos/local siblings without needing to name them.

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 — run a query string against Yahoo web search — and pagination behavior is noted, but there is no explicit when-to-use/when-not guidance and no mention of alternatives (web_search, bing_search, yahoo_search_news). A 3 is the minimum viable here.

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