SocialDataX 微信视频号 WeChat Channels MCP

wechat_get_video_comments_by_url

Read-only

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

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 24, 2026

changedOutput schema / properties / items / items / properties / comment_id / description

Previous value: -"评论 ID"New value: +"微信视频号一级评论 ID；可作为评论回复工具的 comment_id 输入。"

Changed2 schema fields changedAug 17, 2026

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"
+]

Changed1 schema field changedJul 24, 2026

changedOutput schema / properties / items / items / properties / author / properties / user_id / description

Previous value: -"评论作者微信视频号用户 ID；可能是 @finder 或 @stranger；仅 @finder 可用于用户信息工具；不可用时为空字符串"New value: +"评论作者微信视频号用户 ID；可能是 @finder 或 @stranger；仅 v2_...@finder 可用于用户信息工具；不可用时为空字符串"

Changed2 schema fields changedJun 23, 2026

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"
+]

First observedJun 22, 2026

TDQS

A3.8/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 safety profile. The description adds no extra behavioral context (e.g., pagination handling, rate limits, or what happens with invalid URLs). Since annotations carry the safety burden and the description does not contradict them, a neutral score is appropriate.

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, direct sentence states the core purpose with no filler. It is front-loaded with the key verb and resource, making it easy to parse quickly. Every word contributes to understanding.

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 read-only list operation with two parameters, both of which are fully documented in the schema, the description is sufficiently complete. An output schema exists for return values, so the description doesn't need to explain them. The only minor gap is not explicitly noting that the tool is read-only, but that is already in annotations, so the omission is forgiven.

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 coverage is 100%, with detailed descriptions for both 'url' and 'page_token'. The description essentially repeats the URL flexibility (link or shared text) already present in the schema, adding little beyond what structured data provides. The page_token field is not mentioned in the description, but the schema fully explains its pagination semantics, so no loss occurs.

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 action (获取评论列表) and the resource (微信视频号视频链接或包含链接的分享文案). It distinguishes itself from sibling tools like wechat_get_video_comments_by_object_id by specifying the URL-based input, giving agents a precise way to select this tool.

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 specifies the input condition (URL or shared text) but does not explicitly mention when to avoid this tool or point to alternatives such as the object-ID-based sibling. Usage is implied rather than explicitly contrasted with similar tools, so agents must infer which tool to pick based on input type without clear routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SocialDataX 微信视频号 WeChat Channels MCP tools Inspect

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

Need Help?