SocialDataX 红果 Hongguo MCP

hongguo_get_series_comment_replies_by_comment_id

Read-only

读取红果整剧剧评回复，一次返回一页回复正文、作者、根剧评及回复目标和分页信息，不读取单集视频评论。level=2读取主评论下的回复，level=3读取父回复下的楼中楼；保持剧集、评论或父回复及层级不变续页。

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": {
      "series_id": "<series_id>",
      "comment_id": "<comment_id>"
    },
    "name": "hongguo_get_series_comment_replies_by_comment_id"
  }
}

Input Schema

Name	Required	Description
`level`	No	回复层级：2读取主评论下的回复，3读取某条回复下的楼中楼；默认2。
`series_id`	Yes	整部剧的ID，可使用红果搜索结果中的series_id；1至19位正十进制数字字符串，不是单集video_id。
`comment_id`	Yes	1至19位正十进制数字字符串；level=2传整剧剧评列表中的主评论ID，level=3传父回复ID。
`page_token`	No	首屏省略或传空字符串；续页将上一页完整next_page_token原样作为page_token传回。令牌只用于同一整剧；回复还须保持comment_id及level不变，不能修改或跨上下文使用。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/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 genuinely useful behavior beyond that: pagination token must stay bound to the same series, comment_id/parent reply and level, and cannot be reused across contexts. No mention of rate limits or auth, but those are not central for a read tool.

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?

Purpose and scope are front-loaded in the first clause, followed by mode semantics and pagination rules. The second sentence overlaps meaningfully with the schema, but nothing is wasted enough to hurt scanability.

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 full output schema, the description needn't explain return values, and all four parameters are covered. It is complete enough to call correctly across both levels and for continuation; the only soft spot is the un-named video-comment alternative.

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 level, series_id, comment_id and page_token are all already documented in equivalent terms. The description largely restates the schema's level and page_token semantics rather than adding new constraints, so 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+resource (读取红果整剧剧评回复), defines the return unit (一次返回一页) and explicitly excludes single-episode video comments, which cleanly separates it from hongguo_get_video_comment_replies_by_comment_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit conditions for the two modes (level=2 for replies under a main comment, level=3 for nested楼中楼 under a parent reply) and a clear exclusion for video comments. It stops short of naming the video-comment sibling as the alternative, leaving the routing to inference from the exclusion.

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?