Skip to main content
Glama

SocialDataX 知乎 Zhihu MCP

zhihu_get_comment_replies_by_url

Read-only

根据知乎内容页链接和一级评论 ID 读取评论回复。用户已提供完整合法的 content_url 和一级评论 comment_id 时直接使用;已有 content_url 但缺少一级评论 comment_id 时,调用 zhihu_get_content_comments_by_url,复用同一 content_url,并使用一级评论的 items[*].comment_id;缺少内容定位信息时向用户索取;支持使用 page_token 继续翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYes一级评论 ID;用户已提供时直接使用,否则请直接复制 zhihu_get_content_comments_by_url 返回的 items[*].comment_id;不要传评论回复项自身的 comment_id。
page_tokenNo知乎评论回复分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一 content_url 和同一 comment_id 链路;更换链接或一级评论 comment_id 时,请清空 page_token 后从第一页重新读取回复。
content_urlYes知乎内容页面链接;用户已提供时直接使用,否则请直接复用读取该一级评论时使用的回答页链接(包括带视频的回答)、专栏文章链接或独立视频链接;通常直接复用 zhihu_get_content_comments_by_url 使用的 content_url;不要只传 content_id 或数字 ID,不要传接口地址、短链接、移动端链接、包含链接的分享文案、问题页链接或作者主页链接;支持回答页链接 https://www.zhihu.com/question/{question_id}/answer/{answer_id}、专栏文章链接 https://zhuanlan.zhihu.com/p/{article_id}、独立视频链接 https://www.zhihu.com/zvideo/{zvideo_id}。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页评论回复列表;当前页可能为空数组;是否可继续翻页以 next_page_token 是否为空为准。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
reply_countYes该一级评论下的回复总数;不是当前页 items 数量;不可用时为 null。
next_page_tokenYes下一页不透明分页令牌;为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回;只用于当前评论回复续页;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。

TDQS

A4.7/5.0
Behavior4/5

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

readOnlyHint 已表明这是只读操作,描述与此一致,并额外补充了条件分支行为、参数复用链路和分页能力。虽然没有涉及速率限制或错误行为,但对于一个只读查询工具,描述已经提供了足够的行为上下文。

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?

开头一句直接点明核心用途,后续用分号列出条件分支,信息密度高且没有冗余。每个分句都承载决策或操作信息,结构清晰。

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?

对于 3 个参数、有输出 schema、有只读注解的工具,描述覆盖了直接调用、缺失参数时的回退流程、需要向用户追问的场景以及分页继续的方法。Agent 可以据此完成决策和执行,没有明显的信息缺口。

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?

input schema 覆盖率为 100%,参数描述本身已经很详细;描述额外说明了 content_url 与 comment_id 之间的配合关系、如何从 zhihu_get_content_comments_by_url 的返回值中获取 comment_id,以及 page_token 必须原样用于同一链路。

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?

描述明确说明该工具根据知乎内容页链接和一级评论 ID 读取评论回复,动词和资源都很具体。它还与兄弟工具 zhihu_get_content_comments_by_url 形成区分:本工具处理的是评论回复,而非一级评论列表。

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?

描述明确给出了完整决策流程:用户已提供 content_url 和 comment_id 时直接使用;缺少 comment_id 时调用 zhihu_get_content_comments_by_url 并复用同一 content_url 和 items[*].comment_id;缺少内容定位信息时向用户索取;还说明了 page_token 的翻页使用方式。

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.

TDQS

A4.1/5.0
Disambiguation4/5

Each tool maps to a distinct resource and action: search, hot list, content detail, comments, comment replies, user info, user articles, video speech submission/status, and points balance. The only close pair is the two video-submission tools, but their input difference (video URL vs zvideo ID) is clearly stated. Descriptions actively route agents to the right tool based on available identifiers, which reduces ambiguity.

Naming Consistency4/5

Most tools follow the consistent zhihu_<verb>_<object>_by_<identifier> pattern, making the set predictable and readable. The points-balance tool breaks the pattern with the socialdatax_ prefix, and the video speech tools have a longer nested object name but still fit the overall convention. This is a minor deviation rather than a systematic inconsistency.

Tool Count5/5

11 tools is a well-scoped count for a Zhihu content-access MCP, covering search, hot list, content details, comments, user profiles, user articles, video transcription, and account points. Each tool has a concrete purpose, and the set does not feel bloated or overly thin. The dual video-submit tools are mildly redundant but justified by different input identifier types.

Completeness4/5

The core read surface is well covered: hot list, search, content details, comments and replies, user info, user articles, and video speech transcription. One notable gap is that user-posted answers and videos are explicitly excluded from the user articles tool, so that part of a user's Zhihu activity is not accessible. Overall the surface is solid with only minor missing operations.

Resources