SocialDataX 微信视频号 WeChat Channels MCP

wechat_get_video_speech_text_job

Read-only

继续查询用户提供的有效 job_id，或 submit 工具返回的 job_id 对应的微信视频号口播转文字任务状态；每次最多等待 240 秒，不创建新任务或触发重处理。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	口播转文字任务 ID；用户已提供时直接使用，否则使用两个 submit 工具返回的 job_id；不要传 encrypted_object_id、object_id 或视频号作品链接。

Output Schema

TableJSON Schema

Name	Required	Description
`error`	Yes	失败或过期时的稳定错误结构；非终态或成功时为 null。
`job_id`	Yes	任务 ID。
`status`	Yes	任务状态。
`message`	Yes	面向用户/AI 的状态说明。
`platform`	Yes	任务所属平台。
`source_id`	Yes	任务来源 ID。
`content_id`	Yes	平台内容 ID。
`transcript`	Yes	成功时的口播转文字结果；非终态或失败时为 null。
`is_terminal`	Yes	是否已终态。
`next_action`	Yes	非终态时建议的下一步查询动作。
`content_meta`	Yes	作品上下文信息，便于结合转写内容做口播分析。
`content_type`	Yes	内容类型。
`next_poll_after_seconds`	Yes	建议下次查询前等待的秒数；非终态时可用。

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 24, 2026

changedInput schema / properties / job_id / description

Previous value: -"口播转文字任务 ID；必须传两个 submit 工具返回的 job_id；不要传 encrypted_object_id、object_id 或视频号作品链接。"New value: +"口播转文字任务 ID；用户已提供时直接使用，否则使用两个 submit 工具返回的 job_id；不要传 encrypted_object_id、object_id 或视频号作品链接。"

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / job_id / description

Previous value: -"口播转文字任务 ID。"New value: +"口播转文字任务 ID；必须传两个 submit 工具返回的 job_id；不要传 encrypted_object_id、object_id 或视频号作品链接。"

Changed1 schema field changedJul 31, 2026

removedInput schema / properties / wait_seconds

Removed value: -{
-  "default": 0,
-  "description": "可选长轮询等待秒数；0 表示只查询一次，最大 240 秒。",
-  "maximum": 240,
-  "minimum": 0,
-  "type": "integer"
-}

Changed2 schema fields changedJul 30, 2026

changedInput schema / properties / wait_seconds / description

Previous value: -"可选长轮询等待秒数；0 表示只查询一次，最大 900 秒。"New value: +"可选长轮询等待秒数；0 表示只查询一次，最大 240 秒。"

changedInput schema / properties / wait_seconds / maximum
```
Previous value: -900New value: +240
```

Changed2 schema fields changedJul 30, 2026

changedInput schema / properties / wait_seconds / description

Previous value: -"可选长轮询等待秒数；0 表示只查询一次，最大 240 秒。"New value: +"可选长轮询等待秒数；0 表示只查询一次，最大 900 秒。"

changedInput schema / properties / wait_seconds / maximum
```
Previous value: -240New value: +900
```

Changed2 schema fields changedJul 17, 2026

addedInput schema / properties / wait_seconds

Added value: +{
+  "default": 0,
+  "description": "可选长轮询等待秒数；0 表示只查询一次，最大 240 秒。",
+  "maximum": 240,
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / properties / next_action / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "job_id": {
-        "description": "需要继续查询的 job_id。",
-        "type": "string"
-      },
-      "tool_name": {
-        "description": "下一步建议调用的查询工具。",
-        "type": "string"
-      }
-    },
-    "required": [
-      "tool_name",
-      "job_id"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "arguments": {
+        "additionalProperties": true,
+        "description": "下一步查询工具可直接使用的参数。",
+        "type": "object"
+      },
+      "instruction": {
+        "description": "给 AI/客户端的查询指令，说明如何继续轮询到终态。",
+        "type": "string"
+      },
+      "job_id": {
+        "description": "需要继续查询的 job_id。",
+        "type": "string"
+      },
+      "tool_name": {
+        "description": "下一步建议调用的查询工具。",
+        "type": "string"
+      }
+    },
+    "required": [
+      "tool_name",
+      "job_id",
+      "arguments",
+      "instruction"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed3 schema fields changedJul 10, 2026

addedOutput schema / properties / content_id

Added value: +{
+  "description": "平台内容 ID。",
+  "type": "string"
+}

addedOutput schema / properties / content_meta

Added value: +{
+  "additionalProperties": false,
+  "description": "作品上下文信息，便于结合转写内容做口播分析。",
+  "properties": {
+    "author": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "avatar_url": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "作者头像链接。"
+            },
+            "name": {
+              "description": "作者昵称。",
+              "type": "string"
+            },
+            "profile_url": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "作者主页链接。"
+            },
+            "user_id": {
+              "description": "作者用户 ID。",
+              "type": "string"
+            }
+          },
+          "required": [
+            "user_id",
+            "name",
+            "profile_url",
+            "avatar_url"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "作者信息。"
+    },
+    "content_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "作品链接。"
+    },
+    "description": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "平台作品原始描述、正文或配文。"
+    },
+    "duration_ms": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "音视频时长，单位毫秒。"
+    },
+    "title": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "作品标题；平台无标题时为 null。"
+    }
+  },
+  "required": [
+    "content_url",
+    "title",
+    "description",
+    "duration_ms",
+    "author"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "job_id",
-  "status",
-  "is_terminal",
-  "platform",
-  "source_id",
-  "content_type",
-  "transcript",
-  "error",
-  "next_poll_after_seconds",
-  "next_action",
-  "message"
-]New value: +[
+  "job_id",
+  "status",
+  "is_terminal",
+  "platform",
+  "content_id",
+  "source_id",
+  "content_type",
+  "content_meta",
+  "transcript",
+  "error",
+  "next_poll_after_seconds",
+  "next_action",
+  "message"
+]

First observedJun 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint: true, but the description adds valuable context: it waits up to 240 seconds per call and does not create new tasks or trigger reprocessing. This aligns with the read-only annotation and adds specifics about the tool's behavior that the agent needs to know, such as the maximum wait time. No contradiction is present.

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?

The description is a single, focused sentence that front-loads the core action (querying status) and then adds the key constraints (240-second wait, no task creation) without any redundancy. It is efficient and well-structured, with no wasted words.

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 (one parameter), the presence of a detailed schema for that parameter, and annotations covering read-only behavior, the description is complete enough for an agent to call it correctly. It covers what it does, how to get the job_id, and what it doesn't do. The only minor gap is a lack of information about expected response format or failure handling, but since an output schema exists, this is not critical.

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?

The input schema has 100% coverage for the single parameter 'job_id' with a detailed description including instructions and exclusions. The tool description adds no additional parameter-specific information beyond what the schema already provides, so the baseline of 3 is appropriate—the schema does the heavy lifting.

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 purpose: querying the status of a WeChat video speech-to-text task using a job_id. It explicitly distinguishes this from the submit tools by mentioning 'submit 工具返回的 job_id', making the specific resource and action unambiguous. The verb '查询' (query) and the resource '任务状态' are precise, and the sibling comparison is clear.

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

Usage Guidelines4/5

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

The description provides explicit guidance on how to obtain the job_id (user-provided or from submit tools) and what not to pass (encrypted_object_id, object_id, or video links). It also states that no new tasks are created. However, it does not explicitly contrast with alternatives (e.g., 'use this after submitting a job and when polling'), but the context and the mention of submit tools imply the intended usage, so this is clear but could be more explicit.

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?