SocialDataX 红果 Hongguo MCP

hongguo_get_video_comment_replies_by_comment_id

Read-only

读取红果视频主评论下的一页回复，支持剧集单集及独立视频。video_id和comment_id来自视频评论条目；返回回复正文、作者、回复目标及next_page_token。不接收level；整剧剧评及楼中楼使用hongguo_get_series_comment_replies_by_comment_id。续页保持同一视频和主评论，原样传回page_token。

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": {
      "video_id": "<video_id>",
      "comment_id": "<comment_id>"
    },
    "name": "hongguo_get_video_comment_replies_by_comment_id"
  }
}

Input Schema

Name	Required	Description
`video_id`	Yes	红果视频ID，支持剧集单集及独立视频；1至19位正十进制数字字符串。
`comment_id`	Yes	视频评论列表中的主评论ID，1至19位正十进制数字字符串。
`page_token`	No	首屏省略或传空字符串；续页原样传回上一页完整next_page_token，保持视频及回复主评论不变。不能与整剧剧评的分页令牌混用。

Output Schema

Name	Required	Description
`items`	Yes	当前页视频评论回复，保留平台顺序及重复条目。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`reply_count`	Yes	当前视频主评论下的平台回复总数；未提供有效总数时为null，不作为分页结束依据。
`next_page_token`	Yes	下一页不透明分页令牌；为空表示没有下一页。

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real context on pagination (one page, token-based continuation, token not interchangeable with the series-comment token) and on the returned fields (reply text, author, reply target, next_page_token). It does not cover auth or rate limits, which keeps it short of a 5.

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?

Four short sentences, front-loaded with purpose and scope, then provenance, exclusions, and pagination. Dense but each sentence carries actionable information; no filler.

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?

An output schema exists, yet the description still names the key return fields, and it covers the sibling routing, the unsupported parameter, and the continuation protocol. For a 3-parameter paginated read tool, nothing an agent needs to call it 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?

Schema coverage is 100%, so the baseline is 3; the description still adds provenance for video_id and comment_id (taken from video comment entries) and clarifies that page_token must be passed back verbatim while keeping the same video and main comment. The explicit note that level is not accepted also prevents a likely parameter mistake.

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+resource: reads one page of replies under a main comment on Hongguo video, and names the supported video scopes (series episodes and standalone videos). It explicitly distinguishes itself from the sibling series-comment tool, so an agent can pick it without opening either schema.

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 exclusion (does not accept level) and a named alternative: whole-series reviews and nested replies go to hongguo_get_series_comment_replies_by_comment_id. It also states where video_id/comment_id come from and how to continue paging (same video and main comment, pass back page_token unchanged).

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

All SocialDataX 红果 Hongguo 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?