SocialDataX 微信视频号 WeChat Channels MCP

wechat_get_video_detail_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”。

Output Schema

TableJSON Schema

Name	Required	Description
`video`	Yes	视频资源信息；当前不可用时为 null
`author`	Yes	作者信息
`images`	Yes	图文作品按顺序返回图片资源；视频作品为空数组
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`object_id`	Yes	微信视频号详情对象 ID；不可用时为空字符串
`like_count`	Yes	点赞数
`topic_tags`	Yes	作品文案中的话题标签；无话题时为空数组；每项只返回 name
`description`	Yes	作品描述；不可用时为空字符串
`ip_location`	Yes	作品发布时的 IP 属地；没有 IP 属地时为空字符串
`share_count`	Yes	转发/分享数
`content_type`	Yes	内容类型；视频返回 video，图文返回 image
`publish_time`	Yes	发布时间，秒级 Unix 时间戳
`collect_count`	Yes	收藏数
`comment_count`	Yes	评论数
`cover_image_url`	Yes	封面图或图文首图缩略资源链接；当前不可用时为 null
`object_nonce_id`	Yes	微信视频号对象 nonce ID；后续评论等能力需要复用时原样保留

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 26, 2026

changedOutput schema / properties / video / anyOf

Previous value: -[
-  {
-    "properties": {
-      "duration_ms": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "视频时长，单位毫秒；当前不可用时为 null"
-      },
-      "video_url": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "微信视频号视频资源链接；用于后续下载或转附件处理，不保证可直接播放；不可用时为 null。"
-      }
-    },
-    "required": [
-      "video_url",
-      "duration_ms"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "duration_ms": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频时长，单位毫秒；当前不可用时为 null"
+      },
+      "height": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频高度，像素；当前不可用时为 null"
+      },
+      "video_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "微信视频号视频资源链接；用于后续下载或转附件处理，不保证可直接播放；不可用时为 null。"
+      },
+      "width": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频宽度，像素；当前不可用时为 null"
+      }
+    },
+    "required": [
+      "video_url",
+      "duration_ms",
+      "width",
+      "height"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedAug 20, 2026

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

Previous value: -"作者微信视频号用户 ID；仅 v2_...@finder 可用于用户信息或用户发布视频列表工具；不可用时为空字符串"New value: +"作者微信视频号用户 ID；仅 v2_...@finder 可用于用户信息或用户发布作品列表工具；不可用时为空字符串"

changedOutput schema / properties / ip_location / description

Previous value: -"视频发布时的 IP 属地；没有 IP 属地时为空字符串"New value: +"作品发布时的 IP 属地；没有 IP 属地时为空字符串"

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / url / description

Previous value: -"微信视频号视频链接，或包含该链接的分享文案；例如 https://weixin.qq.com/sph/ANxgB9MB8i，或“帮我看下这个视频 https://weixin.qq.com/sph/ANxgB9MB8i”。"New value: +"微信视频号作品链接（视频或图文），或包含该链接的分享文案；例如 https://weixin.qq.com/sph/ANxgB9MB8i，或“帮我看下这个作品 https://weixin.qq.com/sph/ANxgB9MB8i”。"

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: -[
-  "object_id",
-  "object_nonce_id",
-  "content_type",
-  "description",
-  "topic_tags",
-  "cover_image_url",
-  "video",
-  "images",
-  "like_count",
-  "collect_count",
-  "comment_count",
-  "share_count",
-  "publish_time",
-  "ip_location",
-  "author"
-]New value: +[
+  "object_id",
+  "object_nonce_id",
+  "content_type",
+  "description",
+  "topic_tags",
+  "cover_image_url",
+  "video",
+  "images",
+  "like_count",
+  "collect_count",
+  "comment_count",
+  "share_count",
+  "publish_time",
+  "ip_location",
+  "author",
+  "points"
+]

Changed1 schema field changedJul 24, 2026

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

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

Changed2 schema fields changedJul 2, 2026

addedOutput schema / properties / topic_tags

Added value: +{
+  "description": "作品文案中的话题标签；无话题时为空数组；每项只返回 name",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "description": "话题标签名称",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "object_id",
-  "object_nonce_id",
-  "content_type",
-  "description",
-  "cover_image_url",
-  "video",
-  "images",
-  "like_count",
-  "collect_count",
-  "comment_count",
-  "share_count",
-  "publish_time",
-  "ip_location",
-  "author"
-]New value: +[
+  "object_id",
+  "object_nonce_id",
+  "content_type",
+  "description",
+  "topic_tags",
+  "cover_image_url",
+  "video",
+  "images",
+  "like_count",
+  "collect_count",
+  "comment_count",
+  "share_count",
+  "publish_time",
+  "ip_location",
+  "author"
+]

First observedJun 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations (readOnlyHint=true, openWorldHint=true) already establish this as a safe, environment-dependent read operation, and the description is consistent with them. The description adds a mild behavioral nuance—it accepts share text and extracts the link—but adds no context on return shape parsing, error cases, or rate limits. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, tightly written sentence that front-loads the resource (WeChat Channels work), then the input forms, then the action. No filler words, and the sentence order matches how an agent would think about invoking it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (1 param, output schema present, read-only annotations), and the description covers the input essential. The clear gap is routing context: with siblings like wechat_get_video_detail_by_encrypted_object_id and wechat_get_video_comments_by_url in the same family, the description does not help the agent decide between them, relying entirely on tool-name intuition.

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% and the single 'url' parameter is already well documented with examples (raw link and share text containing the link). The description essentially restates the schema's parameter documentation rather than adding new meaning, so the 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?

The description states a specific verb and resource: '获取作品详情' (get work detail) for WeChat Channels, and specifies the input form (video/image-text link or share text containing a link). This is clear, but it does not explicitly contrast with the sibling wechat_get_video_detail_by_encrypted_object_id; differentiation relies on the tool name's 'by_url' suffix rather than an explicit statement.

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?

Usage context is implied: when the agent has a link or share text and wants work details, this tool applies. However, there is no explicit when/when-not guidance or mention of the natural alternative (wechat_get_video_detail_by_encrypted_object_id), leaving the agent to infer routing from naming conventions.

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?