Skip to main content
Glama

SocialDataX 知乎 Zhihu MCP

zhihu_get_content_comments_by_url

Read-only

根据知乎回答页(包括带视频的回答)、专栏文章页或独立视频页链接读取一级评论。支持使用 sort_type 选择排序,并使用 page_token 继续翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sort_typeNo评论排序方式:default=默认,time_descending=最新。如无明确排序需求,保持 default。default
page_tokenNo知乎评论分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一 content_url 和同一排序链路;更换链接或排序时,请清空 page_token 后从第一页重新读取评论。
content_urlYes知乎内容页面链接;只传回答页链接(包括带视频的回答)、专栏文章链接或独立视频链接;从搜索结果中的 answer、article、video 或 videoanswer 读取评论时,直接传该结果里非空的 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本次成功调用的积分消耗与调用完成时的账户积分余额。
comment_countYes该评论区评论数;不是当前页 items 数量;独立视频场景下也不一定等于一级评论总数;不可用时为 null。
next_page_tokenYes下一页不透明分页令牌;为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回;只用于当前评论续页;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already signal readOnlyHint=true, and the description adds meaningful behavioral context: it returns only first-level comments, supports sort_type ordering, and uses page_token for pagination. These traits go beyond the annotation safety profile. However, it does not mention auth prerequisites, rate limits, or invalid-URL behavior, so it stops short of full 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?

The description is a single compact sentence that front-loads the core action and resource, then briefly mentions sorting and pagination. Every clause earns its place; there is no filler, redundancy, or unnecessary verbosity.

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?

Between the detailed parameter schema, the output schema, and the read-only annotations, an agent has almost everything needed to call this tool correctly. The only missing piece is explicit routing to sibling tools, which is already accounted for under usage guidelines. For a read-only paginated comment fetcher, this is sufficiently complete.

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%, with highly detailed parameter descriptions covering page_token opacity rules and content_url format restrictions. The tool description merely restates that sort_type and page_token are supported, adding no new semantic detail beyond the schema. Baseline 3 is 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?

The description opens with '根据知乎回答页...链接读取一级评论', naming a concrete action (read first-level comments) and specific resource types (answer pages, column articles, independent videos). The qualifier '一级评论' clearly distinguishes this tool from the sibling zhihu_get_comment_replies_by_url, which handles nested replies. This satisfies the specific-verb+resource and sibling-differentiation criteria.

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

Usage Guidelines3/5

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

The description implies when to use the tool (when you have a Zhihu content URL and want first-level comments), but it never explicitly states conditions or alternatives such as 'for replies, use zhihu_get_comment_replies_by_url.' The content_url parameter description adds URL-type restrictions, but that is about parameter shaping, not tool selection. Usage guidance remains implied rather than explicit.

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