Skip to main content
Glama

SocialDataX 微信 WeChat MCP

by com.52choujiang
OverviewDiscussionsAdmin

wechat_get_video_comments_by_url

Read-only

根据微信视频号视频链接或包含链接的分享文案获取评论列表。

Input Schema

NameRequiredDescriptionDefault
urlYes微信视频号视频链接，或包含该链接的分享文案；例如 https://weixin.qq.com/sph/ANxgB9MB8i，或“帮我看下这个视频 https://weixin.qq.com/sph/ANxgB9MB8i”。
page_tokenNo评论分页令牌；首次请求留空，继续翻页时必须将上一页返回的完整 next_page_token 原样传回。

Output 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. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / image_urls
      Added value: +{
+  "description": "评论图片完整链接列表；没有时为空数组。链接可能失效，有效期未知；需长期保存时及时下载，图片格式以文件内容为准。",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / items / items / properties / stickers
      Added value: +{
+  "description": "评论表情包列表；按原顺序返回，没有时为空数组",
+  "items": {
+    "properties": {
+      "thumbnail_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "表情包缩略图链接；没有时为 null；链接可能失效，有效期未知"
+      },
+      "url": {
+        "description": "表情包原图链接；可能是静态图片或动图。链接可能失效，有效期未知；需长期保存时及时下载，图片格式以文件内容为准。",
+        "type": "string"
+      }
+    },
+    "required": [
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties / author / properties / has_wechat_channels_account
      Added value: +{
+  "default": false,
+  "description": "是否开通微信视频号",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / comment_id / description
      Previous value: -"评论 ID"New value: +"微信视频号一级评论 ID；可作为评论回复工具的 comment_id 输入。"
  4. 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"
+]
  5. 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 可用于用户信息工具；不可用时为空字符串"
  6. 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"
+]
  7. First observed

TDQS

B3.4/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 safe-read profile is covered. The description adds the useful nuance that input may be raw share text rather than a clean link, but says nothing about rate limits, pagination semantics, or result ordering. Adequate but thin against an annotation-backed baseline.

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?

A single front-loaded sentence that identifies the input forms and the returned resource with zero filler. Nothing is wasted or buried.

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 annotations cover the safety profile, so the description only needs to establish input flexibility and selection context. It handles the former but omits the sibling-routing guidance that would matter most given the crowded comment-tool namespace.

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 both the url and page_token parameters are fully documented in the schema, including the share-text example and the exact next_page_token round-trip rule. The description merely restates the url flexibility and adds no syntax or format detail beyond the schema, 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 (获取) and resource (评论列表) scoped to a WeChat Channels video URL or share text. It is clear what the tool does, but it never distinguishes itself from the close sibling wechat_get_video_comments_by_object_id, which fetches the same resource by a different identifier.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative named. With ~24 siblings including several near-identical comment tools, the agent is left to infer that this one is selected only when it holds a URL rather than an object_id. No prerequisites or exclusions are given.

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