Skip to main content
Glama

SocialDataX 微信 WeChat MCP

by com.52choujiang
OverviewDiscussionsAdmin

wechat_get_video_comments_by_object_id

Read-only

已有同一条视频的 object_id 和 object_nonce_id 时获取评论列表；用户已提供合法组合时直接使用，否则可从作品详情结果或一级评论结果获取；搜索结果只有 encrypted_object_id 时先调用详情工具。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_idYes微信视频号视频的 object_id，例如 14882122090270235141；用户已提供时直接使用，否则可从作品详情或一级评论结果获取；获取评论或评论回复时请与同一条视频的 object_nonce_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本次成功调用的积分消耗与调用完成时的账户积分余额。
comment_countYes评论总数
next_page_tokenYes下一页不透明分页令牌；为空表示没有更多评论。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；next_page_token 只能用于同一微信视频号评论分页链路；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 一起原样传入。"
    • changedOutput schema / properties / items / items / properties / comment_id / description
      Previous value: -"评论 ID"New value: +"微信视频号一级评论 ID；可作为评论回复工具的 comment_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",
-  "comment_count"
-]New value: +[
+  "items",
+  "next_page_token",
+  "comment_count",
+  "points"
+]
  4. Changed1 schema field 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 可用于用户信息工具；不可用时为空字符串"
  5. Changed2 schema fields changed
    • addedOutput schema / properties / comment_count
      Added value: +{
+  "description": "评论总数",
+  "type": "integer"
+}
    • changedOutput schema / required
      Previous value: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "comment_count"
+]
  6. First observed

TDQS

A4.3/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, covering the non-mutating nature and external-world interactions. The description does not contradict these annotations and adds minor context about how to obtain the IDs, but it does not disclose additional behaviors such as rate limits, error handling, or exactly what happens on invalid IDs. Given annotation coverage, this level is acceptable.

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 a single, dense sentence that efficiently conveys the purpose and usage constraints without redundancy. It is front-loaded with the main condition (having the IDs) and then provides actionable routing guidance, maintaining good structure despite being compact.

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 tool's simplicity (comment list retrieval with pagination), the description adequately covers the primary scenario and input requirements. Output schema handles return values, and page_token pagination is documented in the schema. The description also addresses how to obtain IDs when not supplied, making it reasonably complete for an agent to call correctly.

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 description coverage is 100%, so each parameter is already documented. The description adds meaningful value by stating that object_id and object_nonce_id must be passed together and unchanged, and by guiding the agent on where to acquire them if not initially provided. This goes beyond bare schema definitions and clarifies the relationship between the two required parameters.

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 states a specific operation — fetching the comment list for a given video — and explicitly names the required identifiers (object_id and object_nonce_id). It clearly differentiates itself from sibling tools like wechat_get_video_comments_by_url (which uses a URL) and wechat_get_video_comment_replies_by_comment_id (which handles replies), so an agent can distinguish it without inspecting schemas.

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 explicitly states when to use the tool (when object_id and object_nonce_id are already available) and provides fallback sources for obtaining them (from detail or first-level comment results). It also tells the agent to call the detail tool first when only an encrypted_object_id is present, effectively excluding the wrong paths and routing to the correct sibling.

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