Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_get_mp_article_comments_by_url

Read-only

根据微信公众号文章链接或包含链接的分享文案获取评论列表;继续翻页时复用返回的 next_page_token。

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_comments_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes微信公众号文章 / WeChat Official Account article 链接,或包含该链接的分享文案;例如 https://mp.weixin.qq.com/s/cyog0u9QpLFvdBsh9JR3_g。
page_tokenNo公众号文章评论分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇公众号文章的评论分页链路。请在 3 天内继续翻页;令牌失效时请从首页重新获取。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页公众号文章评论
pointsYes本次成功调用的积分消耗与账户积分余额。
comment_countYes文章留言总数,可能包含回复,不等于一级评论条数
featured_countYes精选一级评论总数
next_page_tokenYes公众号文章评论分页令牌;空字符串表示已结束,应停止翻页;非空时将完整令牌原样传回 page_token,并保持文章链接不变;请在 3 天内继续翻页,令牌失效时从首页重新获取。

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. Changed15 schema fields changed
    • addedOutput schema / properties / comment_count / title
      Added value: +"Comment Count"
    • addedOutput schema / properties / featured_count / title
      Added value: +"Featured Count"
    • addedOutput schema / properties / items / items / properties / author / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / items / items / properties / author / title
      Added value: +"WechatMpArticleCommentAuthorData"
    • addedOutput schema / properties / items / items / properties / comment_id / title
      Added value: +"Comment Id"
    • addedOutput schema / properties / items / items / properties / content / title
      Added value: +"Content"
    • addedOutput schema / properties / items / items / properties / ip_location / title
      Added value: +"Ip Location"
    • addedOutput schema / properties / items / items / properties / is_featured / title
      Added value: +"Is Featured"
    • addedOutput schema / properties / items / items / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / items / items / properties / publish_time / title
      Added value: +"Publish Time"
    • addedOutput schema / properties / items / items / properties / reply_count / title
      Added value: +"Reply Count"
    • addedOutput schema / properties / items / items / title
      Added value: +"WechatMpArticleCommentItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / title
      Added value: +"WechatMpArticleCommentsResult"
  4. Changed4 schema fields changed
    • changedInput schema / properties / page_token / description
      Previous value: -"公众号文章评论分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇公众号文章的评论分页链路。"New value: +"公众号文章评论分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇公众号文章的评论分页链路。请在 3 天内继续翻页;令牌失效时请从首页重新获取。"
    • changedOutput schema / properties / comment_count / description
      Previous value: -"文章评论总数"New value: +"文章留言总数,可能包含回复,不等于一级评论条数"
    • changedOutput schema / properties / featured_count / description
      Previous value: -"精选评论总数"New value: +"精选一级评论总数"
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"公众号文章评论分页令牌;空字符串表示已结束,应停止翻页;非空时将完整令牌原样传回 page_token,并保持文章链接不变。"New value: +"公众号文章评论分页令牌;空字符串表示已结束,应停止翻页;非空时将完整令牌原样传回 page_token,并保持文章链接不变;请在 3 天内继续翻页,令牌失效时从首页重新获取。"
  5. Changed1 schema field changed
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"公众号文章评论分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇公众号文章的评论分页链路。"New value: +"公众号文章评论分页令牌;空字符串表示已结束,应停止翻页;非空时将完整令牌原样传回 page_token,并保持文章链接不变。"
  6. 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 safety and external-reach profile is covered. The description adds the pagination-token reuse requirement, which is useful behavior beyond the annotations, but it says nothing about rate limits, empty results, or comment ordering. With annotations carrying the main burden, an added pagination note warrants a 3.

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?

Two compact clauses with no filler; the primary action comes first and the pagination rule follows immediately. Nothing here could be removed without losing information.

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 two-parameter read-only tool with 100% schema coverage, complete annotations, and an output schema covering return values, the description supplies everything needed to call it correctly. The only gap is the lack of disambiguation from the sibling comment-replies tool.

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 schema already documents both url (article link or share text, with an example) and page_token (first request empty, pass full next_page_token, 3-day validity, restart on expiry). The description's phrasing repeats rather than extends that content, so 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 (评论列表) plus the input form (文章链接或含链接的分享文案) and pagination continuation. It does not, however, distinguish itself from the close sibling wechat_get_mp_article_comment_replies_by_url, leaving an agent to infer the difference from the names alone.

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?

The description implies when to use it (when you have an article URL or share text) and hints at the continuation flow ('继续翻页时复用返回的 next_page_token'). It names no alternatives and states no exclusion conditions, so comparative guidance is only implied by sibling names.

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