Skip to main content
Glama

SocialDataX 微信视频号 WeChat Channels MCP

by com.52choujiang
OverviewDiscussionsAdmin

wechat_get_user_info_by_user_id

Read-only

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

Input Schema

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

Output Schema

TableJSON 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. 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，不要传。"
  2. 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，不要传。"
  3. 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"
+]
  4. 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，不要传。"
  5. First observed

TDQS

A3.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, and the description adds no further behavioral context (rate limits, auth, data freshness, or meaning of openWorldHint). It simply restates the purpose without any extra disclosure, so it adds little beyond the annotation.

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 that directly states purpose and usage condition with no filler. Efficient and front-loaded, ideal for a simple tool.

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 1-parameter read-only tool with an output schema, the description combined with the schema covers essentials. Missing explicit error handling and a direct pointer to the URL-based sibling, but those are inferable from the sibling names and schema guardrails.

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?

The schema description for user_id is thorough, covering format, sourcing, and negative conditions. With 100% schema coverage, the tool description needs to add nothing extra, so baseline 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?

States a specific verb and resource: 'get user info' by WeChat Channels user ID. Clearly distinguishes from URL-based sibling (wechat_get_user_info_by_url) and from video-listing tools by explicitly naming the lookup key.

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 description says to use directly when the user provided a valid user_id, and the schema description elaborates where to source the ID otherwise and enforces the v2_...@finder format. It provides a clear condition but stops short of explicitly naming alternatives like the URL-based tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SocialDataX 微信视频号 WeChat Channels MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources