根据公众号账号 ID 获取账号资料。
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | Yes | 公众号账号 ID；可直接使用微信公众号文章详情返回的 account.account_id，例如 gh_114e76fd6e5d。 |
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | 公众号名称；不可用时为空字符串 | |
| points | Yes | 本次成功调用的积分消耗与账户积分余额。 | |
| account_id | Yes | 公众号账号 ID | |
| ip_location | Yes | 公众号 IP 属地；不可用时为空字符串 | |
| linked_video_account | Yes | 关联视频号；当前未关联或不可用时为 null | |
| original_article_count | Yes | 公众号原创文章数；当前不可用时为 null |
Changes observed during successful MCP inspections.
Output schema / properties / points / descriptionPrevious value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"Output schema / properties / points / properties / balance / descriptionPrevious value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"Output schema / properties / points / properties / balance / descriptionPrevious value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"Output schema / properties / points / properties / balance / minimumRemoved value: -0Output schema / properties / account_id / titleAdded value: +"Account Id"Output schema / properties / ip_location / titleAdded value: +"Ip Location"Output schema / properties / linked_video_account / anyOfPrevious value: -[
- {
- "properties": {
- "name": {
- "description": "关联视频号名称；不可用时为空字符串",
- "type": "string"
- },
- "user_id": {
- "description": "关联视频号用户 ID；可用于视频号用户资料或用户发布作品列表工具",
- "type": "string"
- }
- },
- "required": [
- "name",
- "user_id"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "properties": {
+ "name": {
+ "description": "关联视频号名称；不可用时为空字符串",
+ "title": "Name",
+ "type": "string"
+ },
+ "user_id": {
+ "description": "关联视频号用户 ID；可用于视频号用户资料或用户发布作品列表工具",
+ "title": "User Id",
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "user_id"
+ ],
+ "title": "WechatMpLinkedVideoAccountData",
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / name / titleAdded value: +"Name"Output schema / properties / original_article_count / titleAdded value: +"Original Article Count"Output schema / titleAdded value: +"WechatMpAccountInfoResult"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, but the description adds nothing beyond that — no note on what profile fields are returned, whether the lookup fails for invalid IDs, or any rate/auth context. It carries no behavioral information the annotations do not already provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with the resource and lookup key front-loaded and no wasted wording. It is arguably under-specified rather than verbose, but structurally clean.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only tool with a full schema description and an output schema, the description need not explain return values. Still, it could cheaply mention that this returns the account's profile metadata and how it relates to the article/video sibling tools, which it omits entirely.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema description is genuinely helpful, explaining that account_id can be taken from an article detail response with a concrete example (gh_114e76fd6e5d). The description itself adds no parameter meaning, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (获取) and resource (账号资料), so an agent knows this returns profile data rather than articles or posts. However, it is essentially a Chinese restatement of the tool name, offering no differentiation from siblings such as wechat_get_mp_account_articles_by_account_id beyond the resource noun.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of the related sibling tools that take the same account_id. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.