Skip to main content
Glama

SocialDataX 知乎 Zhihu MCP

zhihu_get_user_info_by_profile_url

Read-only

根据知乎用户主页链接读取公开博主资料。

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": {
      "profile_url": "<profile_url>"
    },
    "name": "zhihu_get_user_info_by_profile_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_urlYes知乎用户主页链接;只传 https://www.zhihu.com/people/{url_token} 这种主页链接;不要传 user_id、昵称、回答链接、专栏文章链接、问题页链接、接口地址、短链接、移动端链接或包含链接的分享文案;从用户搜索结果继续时,直接复用所选用户的 items[].profile_url;从内容搜索、详情、评论或评论回复结果继续时,复用所选作者的 author.profile_url。

Output Schema

NameRequiredDescriptionDefault
bioYes知乎用户简介;不可用时为空字符串。
nameYes知乎用户名称;不可用时为空字符串。
genderYes知乎用户性别:male=男,female=女,unknown=未知。
pointsYes本次成功调用的积分消耗与账户积分余额。
user_idYes知乎用户 ID;用于识别博主,不是当前知乎博主资料或作者文章列表输入;不可用时为空字符串。
verifiedYes知乎用户是否为认证账号。
avatar_urlYes用户头像链接;不可用时为 null。
ip_locationYes知乎用户 IP 属地;不可用时为空字符串。
profile_urlYes知乎用户主页链接;可直接复用为 zhihu_get_user_info_by_profile_url 或 zhihu_get_user_posted_articles_by_profile_url 的 profile_url;不可用时为 null。
answer_countYes知乎用户公开回答数;不可用时为 null。
article_countYes知乎用户公开文章数;不可用时为 null。
follower_countYes知乎用户粉丝数;不可用时为 null。
verification_labelYes知乎用户认证文案;不可用时为空字符串。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed13 schema fields changed
    • addedOutput schema / properties / answer_count / title
      Added value: +"Answer Count"
    • addedOutput schema / properties / article_count / title
      Added value: +"Article Count"
    • addedOutput schema / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / bio / title
      Added value: +"Bio"
    • addedOutput schema / properties / follower_count / title
      Added value: +"Follower Count"
    • addedOutput schema / properties / gender / title
      Added value: +"Gender"
    • addedOutput schema / properties / ip_location / title
      Added value: +"Ip Location"
    • addedOutput schema / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / verification_label / title
      Added value: +"Verification Label"
    • addedOutput schema / properties / verified / title
      Added value: +"Verified"
    • addedOutput schema / title
      Added value: +"ZhihuUserInfoData"
  4. 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。"New value: +"知乎用户主页链接;只传 https://www.zhihu.com/people/{url_token} 这种主页链接;不要传 user_id、昵称、回答链接、专栏文章链接、问题页链接、接口地址、短链接、移动端链接或包含链接的分享文案;从用户搜索结果继续时,直接复用所选用户的 items[].profile_url;从内容搜索、详情、评论或评论回复结果继续时,复用所选作者的 author.profile_url。"
  5. First observed

TDQS

A3.6/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, so the safety profile is covered. The description adds one piece of real context — '公开' (public data only) — which tells the agent the result is limited to public profile fields. It does not mention auth requirements, rate limits, or failure behavior for private/deleted users.

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 short sentence, front-loaded with the input (profile URL) followed by the outcome (public author profile). No filler and nothing redundant.

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?

An output schema exists and the sole parameter is fully documented in the schema, so the description does not need to explain return values or input format. What remains thin is the absence of any stated failure/scope conditions for non-public or nonexistent profiles, but overall the definition is sufficient to call the tool correctly.

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 coverage is 100% and the single parameter's description is unusually thorough, listing accepted and rejected URL forms and continuation paths from search/detail/comment results. The tool description adds nothing beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: read a public author profile, keyed by the Zhihu profile URL. An agent can distinguish it from the URL-based siblings (comments, content detail, articles) because the resource is '博主资料' rather than content. It stops short of naming a sibling or contrasting explicitly.

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?

Usage is only implied by the purpose: 'use this when you have a profile URL and want that author's profile'. No when-not guidance or alternative tool is mentioned in the description itself; the useful routing advice (reuse items[].profile_url from user search, author.profile_url from content results) lives only in the schema field description, not the tool description.

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