Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_get_user_info_by_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": {
      "url": "<url>"
    },
    "name": "wechat_get_user_info_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes微信视频号作品链接(视频或图文),或包含该链接的分享文案;例如 https://weixin.qq.com/sph/ANxgB9MB8i,或“帮我看下这个作品 https://weixin.qq.com/sph/ANxgB9MB8i”。

Output Schema

NameRequiredDescriptionDefault
bioYes用户简介;不可用时为空字符串
nameYes用户昵称;不可用时为空字符串
genderYes用户性别
pointsYes本次成功调用的积分消耗与账户积分余额。
user_idYes微信视频号用户 ID;不可用时为空字符串
locationYes用户资料地区;没有资料地区时为空字符串
avatar_urlYes用户头像链接;当前不可用时为 null
ip_locationYes用户 IP 属地;没有 IP 属地时为空字符串
original_content_countYes原创内容数量

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. Changed9 schema fields changed
    • addedOutput schema / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / bio / title
      Added value: +"Bio"
    • addedOutput schema / properties / gender / title
      Added value: +"Gender"
    • addedOutput schema / properties / ip_location / title
      Added value: +"Ip Location"
    • addedOutput schema / properties / location / title
      Added value: +"Location"
    • addedOutput schema / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / original_content_count / title
      Added value: +"Original Content Count"
    • addedOutput schema / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / title
      Added value: +"WechatUserInfoResult"
  4. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"微信视频号视频链接,或包含该链接的分享文案;例如 https://weixin.qq.com/sph/ANxgB9MB8i,或“帮我看下这个视频 https://weixin.qq.com/sph/ANxgB9MB8i”。"New value: +"微信视频号作品链接(视频或图文),或包含该链接的分享文案;例如 https://weixin.qq.com/sph/ANxgB9MB8i,或“帮我看下这个作品 https://weixin.qq.com/sph/ANxgB9MB8i”。"
  5. Changed2 schema fields changed
    • addedOutput schema / properties / points
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
      +  "properties": {
      +    "balance": {
      +      "description": "本次接口完成时看到的当前积分余额。",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "cost": {
      +      "description": "本次请求最终确认消耗的积分。",
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "cost",
      +    "balance"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "user_id",
      -  "name",
      -  "avatar_url",
      -  "bio",
      -  "gender",
      -  "ip_location",
      -  "location",
      -  "original_content_count"
      -]New value: +[
      +  "user_id",
      +  "name",
      +  "avatar_url",
      +  "bio",
      +  "gender",
      +  "ip_location",
      +  "location",
      +  "original_content_count",
      +  "points"
      +]
  6. Added

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 the useful two-step behavior (author is resolved from the URL first, then user info is fetched), but says nothing about failure modes for malformed or non-视频号 links, or whether the parsed author lookup can return multiple candidates.

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?

A single front-loaded sentence with no filler; the input forms and the resulting action are stated in order of what the caller needs to know.

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?

With an output schema present, return values need not be explained, and a one-parameter read tool needs little more. The only residual gap is what happens with an unsupported or non-work link, which is minor at this complexity level.

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 url parameter is already documented with a concrete example in the schema. The description's mention of '视频或图文' and '分享文案' echoes rather than extends the schema, so 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?

The description names a specific verb chain (解析作者后获取用户信息) and the exact resource (微信视频号作品链接/分享文案), which lets an agent distinguish it from wechat_get_user_info_by_user_id (which takes an ID) and wechat_get_video_detail_by_url (which returns the work, not the author). It does not explicitly name the sibling alternative, but the input-based distinction is unambiguous.

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 implied by the input type: use this when you only have a work link or share text and want the author's profile. There is no explicit statement of when not to use it or of the by_user_id alternative for follow-up calls, so the routing must be inferred from the sibling names.

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