Skip to main content
Glama

SocialDataX 红果 Hongguo MCP

hongguo_get_video_comments_by_video_url

Read-only

按红果单集分享链接或包含链接的整段文案读取分享时对应分集的评论。需链接明确包含单集信息;不默认第一集。返回items和next_page_token,条目含video_id,可用于续页或读取回复;整剧剧评使用hongguo_get_series_comments_by_url。

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_url": "<video_url>"
    },
    "name": "hongguo_get_video_comments_by_video_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_urlYes当前支持novelquickapp.com的红果漫剧单集分享链接或包含该链接的完整分享文案,例如https://novelquickapp.com/s/WqCuJHd7dz4/;按分享时的分集获取资源。不要传整剧ID、单集ID或媒体文件地址。
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.5/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 safety profile is covered; the description adds real behavior beyond that: the return shape (items + next_page_token), the presence of video_id in entries usable for paging or fetching replies, and the constraint that page tokens must not be mixed with whole-series review tokens. It stops short of anything about auth, rate limits, or ordering of items, which is why it is not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the core action and the disqualifying condition, then return shape, then the sibling handoff. No filler, no restatement of the tool name, and each clause carries an operational rule.

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 flags the pagination contract and the token-mixing hazard, which is the part an agent most needs before calling twice. Combined with the link-validity constraint and the sibling routing rule, nothing required for a correct invocation is missing for a two-parameter read tool.

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% and both parameters are already well documented in the schema, including the example link format and the page_token continuation rule, so the baseline of 3 applies. The description mostly restates those constraints ('不默认第一集', '链接明确包含单集信息') rather than adding new syntax or format details, though it does hint that video_id enables reply lookups.

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 in the first clause ('读取分享时对应分集的评论' / read the comments of the corresponding episode from a share link) and immediately bounds the scope with '需链接明确包含单集信息;不默认第一集'. It also names a sibling for the adjacent use case (整剧剧评 → hongguo_get_series_comments_by_url), so an agent can route without opening another 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 gives an explicit use condition (a single-episode share link or full share text containing one), explicit exclusions (the link must carry episode info, it does not fall back to episode 1, and per the schema text, do not pass series IDs, episode IDs, or media file URLs), and an explicit alternative for whole-series reviews. When-to-use, when-not-to-use, and the alternative are all present.

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