Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_get_user_info_by_user_id

Read-only

根据微信视频号用户 ID 获取用户信息;用户已提供合法 user_id 时直接使用。

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": {
      "user_id": "<user_id>"
    },
    "name": "wechat_get_user_info_by_user_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes微信视频号用户 ID;只支持以 v2_ 开头、以 @finder 结尾的账号 ID;用户已提供时原样使用,否则可从作品详情、用户发布作品列表、评论或评论回复结果中的 author.user_id 或 reply_to_user_id 复制;如果不是 v2_...@finder,不要传。

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 / user_id / description
      Previous value: -"微信视频号用户 ID;只支持以 v2_ 开头、以 @finder 结尾的账号 ID;从作品详情、用户发布作品列表、评论或评论回复结果中的 author.user_id 或 reply_to_user_id 复制;如果不是 v2_...@finder,不要传。"New value: +"微信视频号用户 ID;只支持以 v2_ 开头、以 @finder 结尾的账号 ID;用户已提供时原样使用,否则可从作品详情、用户发布作品列表、评论或评论回复结果中的 author.user_id 或 reply_to_user_id 复制;如果不是 v2_...@finder,不要传。"
  5. Changed1 schema field changed
    • changedInput schema / properties / user_id / description
      Previous value: -"微信视频号用户 ID;只支持以 v2_ 开头、以 @finder 结尾的账号 ID;从视频详情、用户发布视频列表、评论或评论回复结果中的 author.user_id 或 reply_to_user_id 复制;如果不是 v2_...@finder,不要传。"New value: +"微信视频号用户 ID;只支持以 v2_ 开头、以 @finder 结尾的账号 ID;从作品详情、用户发布作品列表、评论或评论回复结果中的 author.user_id 或 reply_to_user_id 复制;如果不是 v2_...@finder,不要传。"
  6. 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"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / user_id / description
      Previous value: -"微信视频号用户 ID,例如 v2_demo@finder;只支持以 @finder 结尾的账号 ID;从视频详情、用户发布视频列表、评论或评论回复结果中的 author.user_id 或 reply_to_user_id 复制;如果不是 @finder,不要传。"New value: +"微信视频号用户 ID;只支持以 v2_ 开头、以 @finder 结尾的账号 ID;从视频详情、用户发布视频列表、评论或评论回复结果中的 author.user_id 或 reply_to_user_id 复制;如果不是 v2_...@finder,不要传。"
  8. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-network behavior are covered. The description adds only the 'use the provided ID directly' shortcut; it says nothing about lookup cost, failure/empty-result behavior, or resolution of stale IDs. An output schema exists, so return values need not be described, but the behavioral contribution remains thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses, front-loaded with the purpose before the usage rule, with no filler. The second clause slightly overlaps the schema's user_id description, which keeps it from a 5.

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?

For a one-parameter read tool with full schema coverage, annotations, and an output schema, the description covers purpose and the key input-sourcing rule. The only real gap is routing guidance versus the URL-based and search siblings.

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 user_id property already documents the required v2_...@finder format, the prohibition on other formats, and the author.user_id / reply_to_user_id sourcing. The description merely echoes the 'use it directly if provided' rule, adding no new syntax or constraint, 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?

States a specific verb and resource: fetch user info for a WeChat Channels (视频号) user identified BY user_id. The 'by user ID' framing implicitly separates it from the sibling wechat_get_user_info_by_url, so an agent can pick the right entry point, though no sibling is named 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?

Adds one conditional rule: if the user already supplied a valid user_id, use it as-is. It gives no guidance on when to prefer this over wechat_get_user_info_by_url, wechat_search_finder_user, or wechat_get_user_posted_videos_by_user_id, and the alternate sourcing paths live only in the schema.

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