Skip to main content
Glama

SocialDataX 红果 Hongguo MCP

hongguo_get_video_comments_by_video_id

Read-only

按video_id读取一页红果视频评论,支持剧集单集及独立视频,返回正文、作者、计数及next_page_token。剧集分集ID可来自剧集详情的分集列表;有单集分享链接或整段分享文案时使用hongguo_get_video_comments_by_video_url。整剧评分剧评使用hongguo_get_series_comments_by_series_id。回复使用返回的video_id和主评论comment_id调用hongguo_get_video_comment_replies_by_comment_id。

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

Input Schema

NameRequiredDescriptionDefault
video_idYes红果视频ID,支持剧集单集及独立视频;1至19位正十进制数字字符串。
page_tokenNo首屏省略或传空字符串;续页原样传回上一页完整next_page_token,保持视频及回复主评论不变。不能与整剧剧评的分页令牌混用。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页视频评论,保留平台顺序及重复条目。
pointsYes本次成功调用的积分消耗与账户积分余额。
comment_countYes该视频的平台评论总数;未提供有效总数时为null,不作为分页结束依据。
next_page_tokenYes下一页不透明分页令牌;为空表示没有下一页。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/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 description only needs to add context, which it does: results are paged one page at a time and continuation requires passing the previous next_page_token back unchanged. It does not mention ordering of comments, rate limits, or behavior for deleted/hidden comments, so it stops short of full behavioral 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?

Purpose and scope are front-loaded in the first clause, followed by return fields, then one short sentence per alternative tool. Every sentence either scopes the tool or routes the agent elsewhere; nothing is redundant padding.

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, so return values need not be fully explained, and the description still previews body, author, counts, and next_page_token. With two parameters, full schema coverage, and annotations covering the safety profile, nothing an agent needs to call this 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 both parameters are already documented, and the description does not repeat the token rules. It does add meaning beyond the schema by clarifying that video_id supports both series episodes and standalone videos, and by pointing to the episode list as the ID source.

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 opening clause gives a specific verb and resource ('按video_id读取一页红果视频评论') plus scope ('支持剧集单集及独立视频'), and it names the sibling tools it is not (by_video_url, by_series_id, by_comment_id). An agent can distinguish it from the other comment tools without opening any 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?

It routes each adjacent case explicitly: share link or share text goes to hongguo_get_video_comments_by_video_url, whole-series rating reviews go to hongguo_get_series_comments_by_series_id, and replies go to hongguo_get_video_comment_replies_by_comment_id using the returned video_id and comment_id. It also states where a valid episode ID comes from (the series detail episode list), so the agent has both selection and prerequisite guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources