Skip to main content
Glama

SocialDataX 知乎 Zhihu MCP

zhihu_get_content_detail_by_url

Read-only

根据知乎回答页(包括带视频的回答)、专栏文章页或独立视频页链接读取详情。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_urlYes知乎内容页面链接;只传下面三类已支持的知乎网页链接格式,不要传接口地址、短链接、移动端链接或包含链接的分享文案;从搜索结果读取详情时,直接传搜索结果里非空的 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
titleYes内容标题;answer 通常为所属问题标题。
videoYes视频信息;独立视频详情和带视频的回答详情可能返回对象;包含可用时的播放资源 play_url;普通回答、文章或无视频信息时为 null。
authorYes作者信息。
imagesYes正文图片列表,包含链接及宽高;无图时为空数组。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
contentYes详情正文或视频描述纯文本;视频详情不是视频转写;不可用时为空字符串。
questionYes回答所属问题摘要;answer(包括带视频的回答详情)返回对象,article 和独立视频 video 为 null。
content_idYes知乎内容 ID;用于识别内容;不要把 content_id 当作详情或评论输入。
image_urlsYes回答或文章详情正文中解析到的图片链接列表;视频详情返回空数组;无图片时为空数组。
like_countYes喜欢数;与赞同数 upvote_count 不同;不可用时为 null。
topic_tagsYes知乎话题标签列表;无标签时为空数组;每项只返回 name。
content_urlYes可打开的知乎内容页面链接;可作为评论请求的 content_url;不可用时为 null;不要自行拼接。
ip_locationYesIP 属地;不可用时为空字符串。
share_countYes分享数;不可用时为 null。
update_timeYes更新时间,秒级 Unix 时间戳;不可用时为 null。
content_typeYes内容类型:answer=回答(包括带视频的回答详情),article=文章,video=独立视频;详情不会返回 videoanswer。
publish_timeYes发布时间,秒级 Unix 时间戳;不可用时为 null。
upvote_countYes赞同数;不可用时为 null。
collect_countYes收藏数;不可用时为 null。
comment_countYes评论数;不可用时为 null。
cover_image_urlYes封面图链接;不可用时为 null。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the read-only nature of the operation. The description adds useful scope by enumerating supported page types, but does not discuss other behavioral aspects such as rate limits, errors, or response shape; the output schema and annotations cover much of the remaining burden.

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?

One concise, front-loaded sentence conveys the action and all supported content types without filler. It is easy to scan and immediately actionable for an agent.

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?

The description, combined with the read-only annotations, detailed input schema, and presence of an output schema, provides enough information for an agent to correctly select and invoke the tool. There is no critical missing operational guidance.

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 the content_url parameter has a very detailed explanation of accepted URL formats, prohibited input types, and how to pass URLs from search results. The description itself only says 'by URL', adding no parameter semantics beyond what the schema already provides.

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 uses a specific verb ('读取详情') and names the three supported resource types (answer pages including video answers, column articles, and standalone videos). This clearly distinguishes it from sibling tools focused on comments, user profiles, hot lists, and transcription jobs.

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

Usage Guidelines4/5

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

The intended use is clear: pass a supported Zhihu content URL to get its details. The schema adds strong input constraints, but the description itself does not explicitly compare against sibling tools or state when not to use it, so it relies on context rather than explicit exclusion 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