Skip to main content
Glama

SocialDataX 抖音 Douyin MCP

douyin_get_video_speech_text_job

Read-only

根据用户提供的有效 job_id,或 submit 工具返回的 job_id 查询抖音视频口播转文字任务状态;用于继续未完成任务,每次最多等待 240 秒,不触发重处理,也不要重复提交任务。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes口播转文字任务 ID;用户已提供时直接使用,否则使用 submit 工具返回的 job_id;不要传 aweme_id、作品链接或其他 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 / job_id / description
      Previous value: -"口播转文字任务 ID;必须传 submit 工具返回的 job_id,不要传 aweme_id、作品链接或其他 ID。"New value: +"口播转文字任务 ID;用户已提供时直接使用,否则使用 submit 工具返回的 job_id;不要传 aweme_id、作品链接或其他 ID。"
  2. Changed1 schema field changed
    • changedInput schema / properties / job_id / description
      Previous value: -"口播转文字任务 ID。"New value: +"口播转文字任务 ID;必须传 submit 工具返回的 job_id,不要传 aweme_id、作品链接或其他 ID。"
  3. Changed1 schema field changed
    • removedInput schema / properties / wait_seconds
      Removed value: -{
      -  "default": 0,
      -  "description": "可选长轮询等待秒数;0 表示只查询一次,最大 240 秒。",
      -  "maximum": 240,
      -  "minimum": 0,
      -  "type": "integer"
      -}
  4. Changed2 schema fields changed
    • 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
  5. Changed2 schema fields changed
    • 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
  6. Changed2 schema fields changed
    • 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"
      +  }
      +]
  7. 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"
      +]
  8. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds valuable behavioral details: maximum 240-second wait per call and that it does not trigger reprocessing. This goes beyond the annotations and informs the agent of polling behavior and side-effect-free nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single sentence but packs in the purpose, usage context, and key constraints. It is front-loaded with the core action and avoids redundancy. Could be split for readability but is efficient overall.

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 presence of an output schema and the simplicity of a status-polling tool, the description covers what the tool does, when to use it, and key behavioral limits. No critical missing information for correct invocation, though it omits any note about invalid job_id handling, which is minor given the schema guidance.

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 job_id parameter is already fully explained in the schema (use user-provided or submit tool's job_id, not aweme_id or links). The description repeats this but adds no new meaning beyond the schema, so baseline 3 is appropriate.

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 queries the status of a Douyin video speech-to-text task, with specific verb '查询' and resource '任务状态'. This distinguishes it from sibling tools like user info or video detail fetchers, and from the submit tools that create the task.

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 instructs to use a valid job_id from the user or the submit tool, and explicitly says to use it for continuing unfinished tasks. It also warns against resubmitting tasks, which guides the agent toward correct workflow integration with the submit siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources