Crawlora MCP

yahoo_news_comments

Read-only

Fetch a page of top-level comments for a Yahoo News article, including authors, text, reactions, reply counts, and pin status. Use yahoo_news_comment_replies with a returned comment ID for one comment's replies, or yahoo_news_article for the article itself.

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": {
      "content_id": "<content_id>"
    },
    "name": "yahoo_news_comments"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order, defaults to top. Documented values: top, popular, newest, oldest.
`count`	No	Number of comments to return, default 10, clamped to 1..50
`cursor`	No	Pagination cursor from a previous response's next_cursor
`content_id`	Yes	Article id (the id field returned by home/category/article)

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.

Changed4 schema fields changedOct 7, 2026

addedInput schema / properties / content_id / description

Added value: +"Article id (the id field returned by home/category/article)"

addedInput schema / properties / count / description

Added value: +"Number of comments to return, default 10, clamped to 1..50"

addedInput schema / properties / cursor / description

Added value: +"Pagination cursor from a previous response's next_cursor"

addedInput schema / properties / sort / description

Added value: +"Sort order, defaults to top. Documented values: top, popular, newest, oldest."

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/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 genuine context beyond that: it returns only top-level comments (replies excluded) and enumerates the fields returned (authors, text, reactions, reply counts, pin status). It does not mention pagination or rate limits, but the output schema carries the return shape.

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 tight sentences with zero waste. The capability statement is front-loaded and the routing guidance follows immediately.

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?

With a 100%-covered schema, existing annotations, and an output schema, the description provides everything needed to select and call the tool correctly. The 'top-level' scoping and sibling routing are the key pieces, all present; only minor extras like pagination notes are absent, and those live in the schema/output.

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 sort, count, cursor, and content_id are all documented in the schema itself. The description adds no syntax or default details beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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'), resource ('top-level comments for a Yahoo News article'), and scope ('top-level' vs replies). An agent can distinguish this immediately from yahoo_news_comment_replies and yahoo_news_article, which are named explicitly.

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: use yahoo_news_comment_replies with a returned comment ID for a single comment's replies, and yahoo_news_article for the article itself. When-to-use alternatives are fully named with the selecting condition.

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?