Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_get_mp_article_stats_by_url

Read-only

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

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": {
      "url": "<url>"
    },
    "name": "wechat_get_mp_article_stats_by_url"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
pointsYes本次成功调用的积分消耗与账户积分余额。
like_countYes文章点赞数;当前不可用时为 null
read_countYes文章阅读数;当前不可用时为 null
article_urlYes规范化后的公众号文章链接
share_countYes文章分享数;当前不可用时为 null
collect_countYes文章收藏数;当前不可用时为 null
comment_countYes文章评论数;当前不可用时为 null
recommend_countNo文章推荐数(爱心,原在看);与点赞数不同,当前不可用时为 null。

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. Changed8 schema fields changed
    • addedOutput schema / properties / article_url / title
      Added value: +"Article Url"
    • addedOutput schema / properties / collect_count / title
      Added value: +"Collect Count"
    • addedOutput schema / properties / comment_count / title
      Added value: +"Comment Count"
    • addedOutput schema / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / read_count / title
      Added value: +"Read Count"
    • addedOutput schema / properties / recommend_count / title
      Added value: +"Recommend Count"
    • addedOutput schema / properties / share_count / title
      Added value: +"Share Count"
    • addedOutput schema / title
      Added value: +"WechatMpArticleStatsResult"
  4. Changed1 schema field changed
    • addedOutput schema / properties / recommend_count
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "文章推荐数(爱心,原在看);与点赞数不同,当前不可用时为 null。"
      +}
  5. 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"
      +]
  6. Added

TDQS

A3.5/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 safety profile is covered. The description adds one genuinely useful behavioral detail — that a whole share blurb containing the link is accepted, not just a bare URL — but says nothing about whether the article must be public, error behavior for deleted articles, or data freshness.

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?

One sentence, front-loaded with the input form and ending on the output, with no filler. It is efficient, though it is short enough that it could have spent a few more words on scope without becoming bloated.

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-only tool with a full output schema and clear annotations, the description covers what is needed to call it correctly. The remaining omission — what 'interaction statistics' actually comprise — is handled by the output schema, so this is close to complete.

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 single parameter is fully documented with an example URL, so the schema already carries parameter meaning. The description's mention of '分享文案' reinforces the same tolerance but adds no syntax or format detail beyond the schema; 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?

The description states a specific verb and resource (获取…文章互动统计) and specifies the input form (article link or share text containing the link). This distinguishes it from siblings like wechat_get_mp_article_detail_by_url or wechat_get_mp_article_comments_by_url, though it does not name those alternatives 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?

Usage is only implied: an agent can infer it should be used when it has a WeChat article URL and wants engagement metrics. There is no explicit when-to-use versus when-not-to-use guidance, and no mention of the sibling tools that return article detail or comments instead of statistics.

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