Skip to main content
Glama

SocialDataX 红果 Hongguo MCP

hongguo_get_series_comments_by_url

Read-only

按整剧分享链接或包含链接的整段分享文案读取一页红果整剧剧评,返回items与分页信息,条目包含整剧ID,不读取单集视频评论。续页保持同一剧集并将next_page_token原样作为page_token传回;已有series_id时使用hongguo_get_series_comments_by_series_id。剧评回复使用同一条目中的series_id和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": {
      "url": "<url>"
    },
    "name": "hongguo_get_series_comments_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes红果剧集分享链接,或包含该链接的整段分享文案;支持 https://novelquickapp.com/s/836Rt1LxwF4/ 这类链接。一次提供一条剧集链接。
page_tokenNo首屏省略或传空字符串;续页将上一页完整next_page_token原样作为page_token传回。令牌只用于同一整剧;回复还须保持comment_id及level不变,不能修改或跨上下文使用。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页整剧剧评,保留平台顺序,不合并重复条目。
pointsYes本次成功调用的积分消耗与账户积分余额。
comment_countYes平台提供的剧评总数;续页等场景未提供有效总数时为null,不作为分页结束依据。
next_page_tokenYes下一页不透明分页令牌,续页原样作为page_token传回;为空表示没有下一页。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover read-only and open-world access, and the description adds genuine behavioral context beyond them: a page-token is bound to the same 整剧, must be passed back verbatim, and must keep comment_id and level unchanged with no cross-context reuse. It stops short of describing rate limits or what happens on an invalid or expired token, so it is strong but not exhaustive.

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 is front-loaded in the first clause, followed by pagination rules and the sibling alternative in short, clearly separated sentences. A few lines duplicate the schema's page_token wording, which is minor waste but not enough to obscure the guidance.

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?

For a two-parameter read tool with an output schema, everything the agent needs is present: input form, single-link-per-call scope, exclusion of episode comments, continuation protocol, the series_id alternative, and the replies follow-up. Return-value shape is correctly left to the output schema.

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 both url and page_token, including the verbatim next_page_token carry-over. The description largely restates those constraints rather than adding syntax, format, or edge-case meaning beyond them, making the baseline 3 appropriate.

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 and resource (读取一页红果整剧剧评), the accepted input form (整剧分享链接或包含链接的整段分享文案), and what is returned (items 与分页信息). It also explicitly excludes single-episode video comments, distinguishing it from the video-comment siblings without requiring schema inspection.

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?

Names a concrete alternative with the exact selecting condition: 已有series_id时使用hongguo_get_series_comments_by_series_id. It also routes the replies use case to the series_id/comment_id pair and prescribes the pagination continuation procedure, leaving little to inference.

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