Crawlora MCP

yahoo_search

Read-only

Search Yahoo's general web results and return normalized titles, destination URLs, descriptions, and hostnames. Use yahoo_search_news for news, yahoo_search_local for nearby businesses, or yahoo_search_images for image results.

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_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search query
`page`	No	1-based page number, defaults to 1
`time_range`	No	Restrict results by recency. Omit for unfiltered ('Anytime'). Documented values: day, week, month.

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.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / page / description

Added value: +"1-based page number, defaults to 1"

addedInput schema / properties / q / description
```
Added value: +"Search query"
```

addedInput schema / properties / time_range / description

Added value: +"Restrict results by recency. Omit for unfiltered ('Anytime'). Documented values: day, week, month."

First observedOct 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are normalized and lists returned fields, but this is largely redundant with the output schema and does not disclose additional behavior such as pagination limits or result-count constraints.

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, both earning their place. The primary purpose is front-loaded, and the sibling-routing information follows immediately with no filler.

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 general web search tool, the description is complete: purpose, output shape, and disambiguation from sibling search tools. The input schema fully documents parameters and the output schema covers return values, so nothing essential 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 description coverage is 100%, and all three parameters are documented directly in the schema. The description does not add syntax, defaults, or constraints beyond what the schema already provides, so the baseline score of 3 is appropriate.

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's general web results.' It also names the sibling tools for news, local, and images, so an agent can distinguish it from adjacent Yahoo search endpoints without opening their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent to alternatives: use yahoo_search_news for news, yahoo_search_local for nearby businesses, and yahoo_search_images for image results. This gives clear when-to-use-which guidance for the closest siblings.

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.