SocialDataX 微博 Weibo MCP

weibo_submit_video_speech_text_by_post_id

根据微博 post_id 提交视频口播转文字任务；提交后最多等待 240 秒，未完成时返回 job_id 和下一步查询动作。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`post_id`	Yes	微博帖子长 ID；可从搜索、详情、转发或用户帖子列表结果中的 post_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 changedJul 17, 2026

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutation nature is covered. The description adds concrete behavior: waits up to 240 seconds and returns a job_id if incomplete. However, it does not disclose what happens on success (e.g., immediate transcript return) or any side effects like cost or rate limits, which are relevant given the mutable nature.

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 packs the core action, wait duration, and fallback behavior with zero redundancy. Every word earns its place, and it is appropriately sized for the tool's purpose.

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 description covers the essential flow (submit, wait, get job) and references a follow-up query action, which is helpful given the output schema exists to document returns. However, it omits any mention of when to choose this post_id variant over the post_url sibling, which is a significant gap for an agent selecting between them. It also doesn't clarify whether a video must exist on the post.

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 post_id parameter is well-described (long ID, reuse sources). The description merely repeats 'post_id' without adding new meaning, so it meets the baseline but adds no extra value beyond the schema.

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 verb ('submit'), resource ('video speech-to-text task'), and identifier ('post_id'). It clearly distinguishes from the sibling by_post_url variant through the explicit mention of post_id, and the name reinforces it. No ambiguity.

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?

The description gives no guidance on when to use this tool vs the sibling weibo_submit_video_speech_text_by_post_url, nor does it mention prerequisites or follow-up steps beyond a vague '下一步查询动作'. It fails to explicitly state that this variant is for post_id while the other is for URL, leaving the agent to infer from the name alone.

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

All SocialDataX 微博 Weibo 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?