Skip to main content
Glama

SocialDataX 知乎 Zhihu MCP

zhihu_get_user_posted_articles_by_profile_url

Read-only

根据知乎用户主页链接读取该用户发布的文章列表。只返回文章,不返回回答、想法或视频;支持使用 page_token 继续翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_tokenNo知乎用户发布文章列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一 profile_url 的文章列表链路;更换作者时,请清空 page_token 后从第一页重新读取。
profile_urlYes知乎用户主页链接;只传 https://www.zhihu.com/people/{url_token} 这种主页链接;不要传 user_id、昵称、回答链接、专栏文章链接、问题页链接、接口地址、短链接、移动端链接或包含链接的分享文案;从用户搜索结果继续时,直接复用所选用户的 items[].profile_url;从内容搜索、详情、评论或评论回复结果继续时,复用所选作者的 author.profile_url;从博主信息结果继续时,复用返回的 profile_url。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / profile_url / description
      Previous value: -"知乎用户主页链接;只传 https://www.zhihu.com/people/{url_token} 这种主页链接;不要传 user_id、昵称、回答链接、专栏文章链接、问题页链接、接口地址、短链接、移动端链接或包含链接的分享文案;从搜索结果、详情、评论或评论回复里的 author.profile_url 继续读取作者发布文章列表时,或从博主信息结果里的 profile_url 继续读取作者发布文章列表时,直接复用该非空 profile_url。"New value: +"知乎用户主页链接;只传 https://www.zhihu.com/people/{url_token} 这种主页链接;不要传 user_id、昵称、回答链接、专栏文章链接、问题页链接、接口地址、短链接、移动端链接或包含链接的分享文案;从用户搜索结果继续时,直接复用所选用户的 items[].profile_url;从内容搜索、详情、评论或评论回复结果继续时,复用所选作者的 author.profile_url;从博主信息结果继续时,复用返回的 profile_url。"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The readOnlyHint annotation already covers the safety profile. The description adds meaningful behavioral details beyond the annotation: it returns only articles (not answers, thoughts, or videos) and supports pagination via page_token. This is useful context for an agent deciding whether this tool fits the task.

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 two short sentences, front-loaded with the core action and its filter, and ends with the pagination note. No redundant or fluff content; every part earns its place.

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?

Given the detailed schema (100% parameter coverage), annotations, and presence of an output schema, the description covers the essential purpose and return filter. It does not discuss error conditions or edge cases, but those are not critical for correctly invoking the 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%, with thorough parameter descriptions for profile_url and page_token. The tool description itself adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 clearly states the tool reads a user's published article list from their profile URL, and explicitly excludes answers, thoughts, and videos, distinguishing it from sibling content tools. This is a specific verb-resource pairing with a precise scope.

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 tool implies when to use it (retrieving articles for a user) but does not explicitly name sibling alternatives or specify when-not-to-use. The schema parameter description provides guidance on chaining from search results, but the tool description itself lacks explicit routing relative to other zhihu_get_* tools.

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