Skip to main content
Glama

SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_submit_video_speech_text_by_note_id

根据小红书 note_id 提交视频笔记口播转文字任务;提交后最多等待 240 秒,未完成时返回 job_id 和下一步查询动作。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYesnote_id 是小红书笔记 ID。已有完整 note_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 / note_id / description
      Previous value: -"note_id 是小红书笔记 ID。必须原样复制笔记搜索、笔记详情、评论、标签页笔记列表或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。"New value: +"note_id 是小红书笔记 ID。已有完整 note_id 时原样使用;否则可从笔记搜索、笔记详情、评论、标签页笔记列表或用户发帖列表结果复制;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。"
  2. Changed1 schema field changed
    • changedInput schema / properties / note_id / description
      Previous value: -"note_id 是小红书笔记 ID。必须原样复制搜索、详情、评论、标签页笔记列表或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。"New value: +"note_id 是小红书笔记 ID。必须原样复制笔记搜索、笔记详情、评论、标签页笔记列表或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。"
  3. Changed1 schema field changed
    • changedInput schema / properties / note_id / description
      Previous value: -"note_id 是 24 位小写十六进制稳定笔记 ID。必须原样复制搜索、详情、评论、标签页笔记或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。"New value: +"note_id 是小红书笔记 ID。必须原样复制搜索、详情、评论、标签页笔记列表或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。"
  4. Changed1 schema field changed
    • changedInput schema / properties / note_id / description
      Previous value: -"note_id 是 24 位小写十六进制稳定笔记 ID。必须原样复制搜索、详情、评论或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。"New value: +"note_id 是 24 位小写十六进制稳定笔记 ID。必须原样复制搜索、详情、评论、标签页笔记或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。"
  5. 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"
      +  }
      +]
  6. 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"
      +]
  7. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate this is a mutating, non-idempotent operation. The description adds valuable behavioral details: it waits up to 240 seconds, returns a job_id when incomplete, and tells the agent to perform a follow-up query. It does not contradict any annotations; the added info is complementary.

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 sentence that front-loads the action and then states the waiting behavior and the fallback return. No filler words; every clause carries information.

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?

With one parameter, an output schema present, and sibling tools for follow-up, the description covers the essential workflow: submit, wait, and query next. It does not explicitly name the exact follow-up tool, but the mention of a 'next query action' is sufficient for an agent to infer the step, especially with sibling visibility.

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 schema description for note_id is highly detailed (100% coverage), specifying how to obtain it and what not to do with it. The tool description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 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 states a specific verb ('submit'), a clear resource ('video note speech-to-text task'), and the identifier type (note_id). It also distinguishes from the sibling tool that uses note_url, making the purpose unambiguous and separable from the other submission tool.

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 use when you have a note_id, but does not explicitly mention the alternative (xhs_submit_video_speech_text_by_note_url) or when to choose one over the other. It provides no explicit usage exclusions, but the sibling tools are visible to the agent, so the context is partially inferred.

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