Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

yahoo_news_comments

Fetch Yahoo News article comments by article ID, including author, body, reactions, reply counts, pin status, with sorting and cursor pagination.

Instructions

Yahoo News article comments. Returns a page of an article's top-level comments: author, body, reaction counts, reply count, and pin status, with sort order and cursor-based pagination. Sourced from Yahoo's own comment platform gateway.

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
`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)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.17.5Sep 26, 2026
- addedInput schema / properties / sort / enum
```
Added value: +[
+  "top",
+  "popular",
+  "newest",
+  "oldest"
+]
```
Addedv1.14.0Aug 21, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the read-only nature ('Returns'), pagination behavior, sort order, and the specific data fields included, plus the data source. It does not mention rate limits or authentication, but for a simple fetch tool this is a reasonably transparent disclosure.

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?

Three sentences with no fluff. The lead phrase 'Yahoo News article comments' immediately identifies the resource, followed by return details, pagination, and source. Every sentence earns its place.

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?

There is no output schema, so the description must explain return values, and it does list the fields and pagination. It does not explicitly describe the response container (e.g., array vs. object with next_cursor), but the cursor parameter's schema description hints at the pagination structure. For a tool of this complexity, it is largely complete.

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 the schema already documents all parameters. The description adds context for sort and cursor ('sort order and cursor-based pagination') but does not add meaning for content_id beyond what the schema provides. This meets the baseline without exceeding it.

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?

The description states a specific verb and resource: 'Returns a page of an article's top-level comments' with the exact fields returned (author, body, reaction counts, reply count, pin status). It distinguishes itself from the sibling yahoo_news_comment_replies by explicitly saying 'top-level comments' and mentioning reply count, making the boundary clear.

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?

The description implies usage context through 'Yahoo News article comments' and 'top-level comments,' but it does not explicitly name alternatives or state when not to use this tool. The distinction from yahoo_news_comment_replies is implied rather than stated, so an agent must infer the boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server