Skip to main content
Glama

SocialDataX 微信 WeChat MCP

by com.52choujiang
OverviewDiscussionsAdmin

wechat_get_video_comment_replies_by_comment_id

Read-only

根据同一条视频的 object_id、object_nonce_id 和一级评论 comment_id 获取评论回复；用户已提供完整合法的 ID 组合时直接使用；已有作品链接、encrypted_object_id 或完整 object_id + object_nonce_id 组合但缺少必需 ID 时，按已有输入调用相应工具，从作品详情结果或一级评论结果补全；缺少作品定位信息时向用户索取；不要传回复项的 comment_id。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_idYes微信视频号视频的 object_id，例如 14882122090270235141；用户已提供时直接使用，否则可从作品详情或一级评论结果获取；获取评论或评论回复时请与同一条视频的 object_nonce_id 一起原样传入。
comment_idYes微信视频号一级评论 ID，例如 14941641522352032263；用户已提供时直接使用，否则从一级评论结果 items[].comment_id 复制；不要传回复项的 comment_id。
page_tokenNo评论回复分页令牌；首次请求留空，继续翻页时必须将上一页返回的完整 next_page_token 原样传回；只能用于同一微信视频号、同一一级评论的回复分页链路。
object_nonce_idYes微信视频号视频的 object_nonce_id，例如 12801331239707625908_0_39_0_0；用户已提供时直接使用，否则可从作品详情或一级评论结果获取；获取评论或评论回复时请与同一条视频的 object_id 一起原样传入。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页评论回复列表；过滤后可能为空数组
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
next_page_tokenYes下一页不透明分页令牌；为空表示没有更多评论回复。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；next_page_token 只能用于同一微信视频号、同一一级评论的回复分页链路；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / comment_id / description
      Previous value: -"微信视频号一级评论 ID，例如 14941641522352032263；从一级评论结果 items[].comment_id 复制，用于获取该评论下的回复；不要传回复项的 comment_id。"New value: +"微信视频号一级评论 ID，例如 14941641522352032263；用户已提供时直接使用，否则从一级评论结果 items[].comment_id 复制；不要传回复项的 comment_id。"
    • changedInput schema / properties / object_id / description
      Previous value: -"微信视频号视频的 object_id，例如 14882122090270235141；获取评论或评论回复时请与同一条视频的 object_nonce_id 一起原样传入。"New value: +"微信视频号视频的 object_id，例如 14882122090270235141；用户已提供时直接使用，否则可从作品详情或一级评论结果获取；获取评论或评论回复时请与同一条视频的 object_nonce_id 一起原样传入。"
    • changedInput schema / properties / object_nonce_id / description
      Previous value: -"微信视频号视频的 object_nonce_id，例如 12801331239707625908_0_39_0_0；获取评论或评论回复时请与同一条视频的 object_id 一起原样传入。"New value: +"微信视频号视频的 object_nonce_id，例如 12801331239707625908_0_39_0_0；用户已提供时直接使用，否则可从作品详情或一级评论结果获取；获取评论或评论回复时请与同一条视频的 object_id 一起原样传入。"
    • changedOutput schema / properties / items / items / properties / comment_id / description
      Previous value: -"评论回复 ID"New value: +"微信视频号评论回复自身 ID；不是一级评论 ID，不要作为评论回复入口输入。"
  2. Changed2 schema fields changed
    • changedInput schema / properties / object_id / description
      Previous value: -"微信视频号视频的 object_id，例如 14882122090270235141；获取评论时请与同一条视频的 object_nonce_id 一起原样传入。"New value: +"微信视频号视频的 object_id，例如 14882122090270235141；获取评论或评论回复时请与同一条视频的 object_nonce_id 一起原样传入。"
    • changedInput schema / properties / object_nonce_id / description
      Previous value: -"微信视频号视频的 object_nonce_id，例如 12801331239707625908_0_39_0_0；获取评论时请与同一条视频的 object_id 一起原样传入。"New value: +"微信视频号视频的 object_nonce_id，例如 12801331239707625908_0_39_0_0；获取评论或评论回复时请与同一条视频的 object_id 一起原样传入。"
  3. Changed2 schema fields changed
    • addedOutput schema / properties / points
      Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "points"
+]
  4. Changed2 schema fields changed
    • changedOutput schema / properties / items / items / properties / author / properties / user_id / description
      Previous value: -"评论作者微信视频号用户 ID；可能是 @finder 或 @stranger；仅 @finder 可用于用户信息工具；不可用时为空字符串"New value: +"评论作者微信视频号用户 ID；可能是 @finder 或 @stranger；仅 v2_...@finder 可用于用户信息工具；不可用时为空字符串"
    • changedOutput schema / properties / items / items / properties / reply_to_user_id / description
      Previous value: -"被回复用户 ID；可能是 @finder 或 @stranger；仅 @finder 可用于用户信息工具；不可用时为空字符串"New value: +"被回复用户 ID；可能是 @finder 或 @stranger；仅 v2_...@finder 可用于用户信息工具；不可用时为空字符串"
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds valuable behavioral context: the requirement that object_id and object_nonce_id must come from the same video and be passed together, and the rationale for obtaining missing IDs via other tools. There is no contradiction with annotations.

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?

The description is somewhat long but efficiently packed with actionable guidance. It opens with the core purpose, then provides structured usage scenarios. No filler sentences; every clause contributes to correct tool invocation.

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?

Given the presence of an output schema, the description doesn't need to explain return formats. It covers when to use, how to handle missing inputs, and usage constraints. The pagination mechanism is described in the page_token parameter. A minor gap is the lack of explicit mention of rate limits or error handling, but these are not critical for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions including examples. The description adds workflow-level semantics: emphasizing same-video pairing of object_id and object_nonce_id, insisting comment_id be a top-level comment (not a reply), and detailing page_token reuse across pages. This goes beyond the schema's basic definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: retrieving comment replies for a specific video based on object_id, object_nonce_id, and comment_id. It distinguishes itself from sibling tools like wechat_get_video_comments_by_object_id (which fetches top-level comments) by focusing on replies, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: use directly when full ID combos are provided; call other tools to complete missing IDs when partial info exists; ask user for video location info when absent. It also explicitly warns not to pass a reply's comment_id, preventing a common misuse.

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