Crawlora MCP

yahoo_news_comment_replies

Read-only

Fetch a page of replies to one Yahoo News comment, with authors, comment text, and reaction counts. Start with yahoo_news_comments for an article's top-level comments, then pass a returned comment ID here to read its thread.

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>",
      "comment_id": "<comment_id>"
    },
    "name": "yahoo_news_comment_replies"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order, defaults to newest. Documented values: newest, oldest.
`count`	No	Number of replies to return, default 10, clamped to 1..50
`cursor`	No	Pagination cursor from a previous response's next_cursor
`comment_id`	Yes	Parent comment id (the id field returned by /yahoo-news/comments)
`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.

Changed5 schema fields changedOct 7, 2026

addedInput schema / properties / comment_id / description

Added value: +"Parent comment id (the id field returned by /yahoo-news/comments)"

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 replies 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 newest. Documented values: 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 and openWorldHint, so safety is covered; the description adds useful behavioral context about what the response contains (authors, text, reaction counts) and that results are paged. It stops short of describing pagination termination or ordering defaults, but with annotations carrying the safety profile this is solid.

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, front-loaded with the operation and followed by the prerequisite workflow. No filler or restatement of 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?

With an output schema present, return fields need not be explained, yet the description still summarizes them. The paginated nature is acknowledged via 'a page'; cursor mechanics are left to the schema, which is reasonable.

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 coverage is 100%, with comment_id and content_id already documented as IDs returned by /comments and article endpoints. The description reinforces the comment_id provenance but adds no syntax, format, or defaulting detail beyond the schema, so the 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: fetching a page of replies to one Yahoo News comment. It also enumerates the payload (authors, comment text, reaction counts) and explicitly contrasts itself with yahoo_news_comments, so an agent can distinguish the two without inspecting 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?

Gives an explicit ordered workflow: start with yahoo_news_comments for top-level comments, then feed a returned comment ID into this tool. It names the alternative tool and the precondition that selects it, leaving nothing to inference.

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?