Skip to main content
Glama

SocialDataX 微信视频号 WeChat Channels MCP

by com.52choujiang
OverviewDiscussionsAdmin

wechat_get_user_info_by_url

Read-only

根据微信视频号作品链接（视频或图文）或分享文案解析作者后获取用户信息。

Input Schema

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

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 / 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”。"
  2. 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"
+]
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations include readOnlyHint: true, which already indicates a safe read operation. The description adds the behavioral detail that the tool parses the author from the URL or share text before fetching user info, and that it supports both video and graphic links. This adds value beyond the annotations, though it does not disclose potential failure modes or rate limits, keeping it at a 4 rather than a 5.

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 a single, concise sentence that is front-loaded with the core purpose and directly states the input type and outcome. There is zero redundancy or wasted wording; every phrase adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter), the presence of an output schema, and annotations that declare read-only and open-world behavior, the description is fully sufficient. It explains what the tool does, how it works (parsing), and the input format. No additional details are required.

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 input schema already provides a comprehensive description of the 'url' parameter (including examples and acceptable formats) with 100% coverage. The description adds no additional parameter semantics beyond restating that the tool parses the author, which is not needed given the schema's detail. Baseline 3 is correct when the schema carries the parameter documentation burden.

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's function: given a WeChat Channels video/post link or shared text, it parses the author and retrieves user information. It uses a specific verb (获取) and resource (用户信息), and distinguishes from sibling tools like wechat_get_user_info_by_user_id by explicitly mentioning the URL-based approach.

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 provides clear context on when to use this tool (when you have a work link or share text), but it does not explicitly mention alternatives or exclusions. The sibling tools suggest there is a by-user-id variant, but the description does not state to use that when a user ID is available. This is implied but not stated, so a 4 is appropriate.

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