Skip to main content
Glama

SocialDataX 快手 Kuaishou MCP

by com.52choujiang
OverviewDiscussionsAdmin

kuaishou_submit_video_speech_text_by_photo_id

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
photo_idYes快手作品 photo_id；用户已提供时直接使用，否则可从包含 photo_id 的快手作品结果中复用。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorYes失败或过期时的稳定错误结构；非终态或成功时为 null。
job_idYes任务 ID。
statusYes任务状态。
messageYes面向用户/AI 的状态说明。
platformYes任务所属平台。
source_idYes任务来源 ID。
content_idYes平台内容 ID。
transcriptYes成功时的口播转文字结果；非终态或失败时为 null。
is_terminalYes是否已终态。
next_actionYes非终态时建议的下一步查询动作。
content_metaYes作品上下文信息，便于结合转写内容做口播分析。
content_typeYes内容类型。
next_poll_after_secondsYes建议下次查询前等待的秒数；非终态时可用。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / photo_id / description
      Previous value: -"快手作品 photo_id；可从包含 photo_id 的快手作品结果中复用。"New value: +"快手作品 photo_id；用户已提供时直接使用，否则可从包含 photo_id 的快手作品结果中复用。"
  2. Changed1 schema field changed
    • 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"
+  }
+]
  3. Changed3 schema fields changed
    • 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"
+]
  4. Added

TDQS

A4/5.0
Behavior4/5

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

The description adds valuable behavior beyond annotations: it discloses a 240-second wait and the fallback of returning job_id when incomplete, along with pointing to a next query action. Annotations already indicate it's non-read-only and non-idempotent, so the description complements rather than repeats.

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 concise sentence that packs the core action, timeout, and fallback behavior without fluff. It is appropriately short and front-loaded.

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?

The description covers the essential invocation semantics: how to submit, the wait, and the fallback job_id. With an output schema present and the sibling getter tool listed, the agent has enough context. It could explicitly mention the sibling for URL-based submission, but that's a minor omission.

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 the photo_id parameter described in the schema as '快手作品 photo_id；用户已提供时直接使用，否则可从包含 photo_id 的快手作品结果中复用', which provides sourcing guidance. The tool description itself adds nothing about the parameter, but since the schema covers it, the baseline 3 suffices.

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: submitting a video speech-to-text task based on photo_id. It uses a specific verb (提交) and resource (视频口播转文字任务), and the photo_id basis distinguishes it from the sibling tool that uses video_url.

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 implies usage when a photo_id is available and mentions reuse from results, but it does not explicitly contrast with the sibling tool for video URL submission or the job query tool. The agent must infer from sibling names rather than receive direct 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 快手 Kuaishou 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