Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_news_category

Fetch Yahoo News section stories with titles, URLs, summaries, and publish times. Specify category: us, world, politics, science, weather-news, or originals.

Instructions

Yahoo News section story stream. Returns a Yahoo News section's story stream: title, destination URL, summary, source, publish time, comment count, and thumbnail images for each story. Sourced from Yahoo News's own server-rendered section pages.

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": {
      "category": "<category>"
    },
    "name": "yahoo_news_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesYahoo News section

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / category / enum
      Added value: +[
+  "us",
+  "world",
+  "politics",
+  "science",
+  "weather-news",
+  "originals"
+]
  2. Addedv1.14.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully discloses that data is sourced from Yahoo News's server-rendered section pages and lists returned fields, but it omits pagination behavior, result limits, freshness, or error conditions. This is adequate but not rich.

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?

The description is compact and front-loaded: the first sentence names the resource, and the second sentence adds specific return fields. It avoids filler, though the opening fragment 'Yahoo News section story stream' is slightly redundant with the tool name.

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 simple one-parameter read tool with no output schema, the description provides enough information to call it correctly: the enum in the schema covers the category, and the description covers what will be returned. It lacks pagination or limits detail, but that is a minor gap given the tool's low complexity.

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?

The sole parameter `category` is already documented in the schema with an enum of valid Yahoo News sections, and schema coverage is 100%. The description adds little beyond the schema, 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as returning a Yahoo News section story stream and enumerates the exact output fields (title, URL, summary, source, publish time, comment count, thumbnails). It distinguishes the tool as section-scoped, but does not explicitly differentiate it from siblings like yahoo_news_home or yahoo_news_article, so it stops short of a 5.

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 description: an agent should call this when it needs a category's story stream rather than a single article or homepage feed. However, it does not explicitly state when to use this tool versus alternatives such as yahoo_news_home, yahoo_news_article, or yahoo_news_suggest.

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