Crawlora MCP

yahoo_news_home

Read-only

Fetch story items from Yahoo News's curated homepage need-to-know stream, with title, destination URL, summary, source, publish time, comment count, and thumbnails. Use yahoo_news_category for a topic feed, yahoo_news_related for related coverage, or yahoo_news_article for one story's details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "yahoo_news_home"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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.

First observedOct 5, 2026

TDQS

A4.4/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 and openness profile is covered. The description adds that this is a 'curated ... need-to-know stream', which tells the agent the content is editorially selected rather than a search result. It says nothing about how fresh the stream is, pagination, or rate limits, so it only adds modest value on top of the annotations.

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?

Two sentences, front-loaded with the primary purpose and followed immediately by the routing guidance. The middle enumeration of return fields is the one soft spot: it restates what the output schema already carries, making it the only sentence content that does not fully earn its place.

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?

Zero parameters, an output schema, and readOnly/openWorld annotations mean the description has little else to carry, and it covers purpose and sibling routing fully. Nothing an agent needs in order 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.

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. The field list (title, URL, summary, source, publish time, comment count, thumbnails) describes output rather than input and is largely redundant given an output schema exists.

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 ('Fetch story items') plus the exact resource ('Yahoo News's curated homepage need-to-know stream'), which is a distinct feed from any category/related/article sibling. An agent can identify the source of content without opening a schema, since there are no parameters to disambiguate it.

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 three alternatives with the condition that selects each: yahoo_news_category for a topic feed, yahoo_news_related for related coverage, yahoo_news_article for one story's details. This is a complete when-to-use mapping rather than an implied one.

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.

Resources

Need Help?