Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_get_mp_article_comment_replies_by_url

Read-only

根据微信公众号文章链接(或包含链接的分享文案)获取评论回复;可传一级评论 ID 指定评论,省略时自动选择有回复的评论。

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

Input Schema

NameRequiredDescriptionDefault
urlYes微信公众号文章 / WeChat Official Account article 链接,或包含该链接的分享文案;例如 https://mp.weixin.qq.com/s/cyog0u9QpLFvdBsh9JR3_g。
comment_idNo公众号一级评论 ID;从评论结果 items[].comment_id 复制。首次请求可留空,此时由服务自动选择有回复的评论;不要传评论回复 ID。
page_tokenNo公众号文章评论回复分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇文章下同一条一级评论的回复分页链路。请在 3 天内继续翻页;令牌失效时请从首页重新获取。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页公众号文章评论回复
pointsYes本次成功调用的积分消耗与账户积分余额。
reply_countYes该一级评论的回复总数
next_page_tokenYes公众号文章评论回复分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_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. Changed14 schema fields changed
    • 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_ai_generated / title
      Added value: +"Is Ai Generated"
    • addedOutput schema / properties / items / items / properties / is_featured / title
      Added value: +"Is Featured"
    • addedOutput schema / properties / items / items / properties / parent_comment_id / title
      Added value: +"Parent Comment Id"
    • addedOutput schema / properties / items / items / properties / publish_time / title
      Added value: +"Publish Time"
    • addedOutput schema / properties / items / items / title
      Added value: +"WechatMpArticleCommentReplyItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / properties / reply_count / title
      Added value: +"Reply Count"
    • addedOutput schema / title
      Added value: +"WechatMpArticleCommentRepliesResult"
  4. Changed2 schema fields changed
    • changedInput schema / properties / page_token / description
      Previous value: -"公众号文章评论回复分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇文章下同一条一级评论的回复分页链路。"New value: +"公众号文章评论回复分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇文章下同一条一级评论的回复分页链路。请在 3 天内继续翻页;令牌失效时请从首页重新获取。"
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"公众号文章评论回复分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇文章下同一条一级评论的回复分页链路。"New value: +"公众号文章评论回复分页令牌;首次请求留空,继续翻页时将上一页返回的完整 next_page_token 原样传回;只能用于同一篇文章下同一条一级评论的回复分页链路。请在 3 天内继续翻页;令牌失效时请从首页重新获取。"
  5. 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 non-obvious behavior beyond that: omission of comment_id triggers automatic selection of a comment that has replies. It says nothing about pagination lifecycles or empty-result behavior, which the schema's page_token text partially covers instead.

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?

A single semicolon-joined sentence with the resource and input form front-loaded, then the optional-parameter behavior. No filler, though the two clauses could be split for readability.

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?

An output schema exists, so return values need not be explained, and the schema carries the parameter detail. Purpose plus the auto-selection behavior is enough for an agent to call this correctly; only the relationship to the sibling comments tool is left unstated.

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%, so all three parameters are already documented in detail, including the 3-day page_token validity and the warning not to pass a reply ID. The description adds only a compressed restatement of the comment_id semantics, 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?

States a specific verb+resource: retrieve comment replies (评论回复) for a WeChat Official Account article given its URL or share text. The '回复' framing distinguishes it from the sibling wechat_get_mp_article_comments_by_url, though that sibling is never named, so the differentiation is implicit rather than explicit.

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?

It explains the key decision inside this tool – pass a first-level comment_id to target a specific comment, or omit it and the service auto-selects a comment that has replies – which is genuine when-to-use guidance. It never states when to use this instead of the sibling comments tool, so an agent must infer that replies require a parent comment that already exists.

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