Skip to main content
Glama

SocialDataX 微信 WeChat MCP

by com.52choujiang
OverviewDiscussionsAdmin

wechat_get_mp_article_stats_by_url

Read-only

根据微信公众号文章链接或包含链接的分享文案获取文章互动统计。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes微信公众号文章 / WeChat Official Account article 链接，或包含该链接的分享文案；例如 https://mp.weixin.qq.com/s/cyog0u9QpLFvdBsh9JR3_g。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
like_countYes文章点赞数；当前不可用时为 null
read_countYes文章阅读数；当前不可用时为 null
article_urlYes规范化后的公众号文章链接
share_countYes文章分享数；当前不可用时为 null
collect_countYes文章收藏数；当前不可用时为 null
comment_countYes文章评论数；当前不可用时为 null

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / wow_count
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "文章在看数（Wow）；当前不可用时为 null"
-}
    • changedOutput schema / required
      Previous value: -[
-  "article_url",
-  "read_count",
-  "like_count",
-  "share_count",
-  "collect_count",
-  "comment_count",
-  "wow_count",
-  "points"
-]New value: +[
+  "article_url",
+  "read_count",
+  "like_count",
+  "share_count",
+  "collect_count",
+  "comment_count",
+  "points"
+]
  2. 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 tool is known to be read-only. The description adds no further behavioral context, such as what specific stats are returned or any caveats about invalid URLs. It does not contradict annotations, but adds minimal value beyond them.

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 sentence that is directly to the point, with no filler or redundancy. It is efficiently front-loaded with the core purpose.

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 only one parameter, an output schema present, and annotations covering read-only behavior, the description is largely sufficient for an agent to call the tool correctly. The only minor gap is the lack of specificity about what 'interaction statistics' includes, but this is not essential for invocation.

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 parameter 'url' is already well documented with an explanation and example. The tool description does not add any additional meaning about the parameter, so the baseline of 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 states a specific verb ('获取' / get), resource ('公众号文章' / WeChat Official Account article), and outcome ('互动统计' / interaction statistics). It clearly distinguishes this from sibling tools like comments, detail, or user info, since it focuses on statistics rather than content or user data.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description implies it is for retrieving interaction statistics, but it does not mention exclusions or point to siblings like get_mp_article_detail for content or get_mp_article_comments for comments.

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

All SocialDataX 微信 WeChat 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