SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_submit_video_speech_text_by_note_url

根据小红书视频笔记链接、短链接或分享文案提交口播转文字任务；提交后最多等待 240 秒，未完成时返回 job_id 和下一步查询动作。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "note_url": "<note_url>"
    },
    "name": "xhs_submit_video_speech_text_by_note_url"
  }
}

Input Schema

Name	Required	Description	Default
`note_url`	Yes	小红书视频笔记链接、短链接或分享文案。

Output 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"
+]

AddedJun 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag this as a write operation (readOnlyHint=false, idempotentHint=false). The description adds valuable behavioral detail beyond annotations: it explicitly mentions a 240-second wait and that an incomplete job returns a job_id and points to a next query action. This goes beyond the structured hints and clarifies the asynchronous nature of the task.

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, dense sentence that front-loads the core action (submit task by note URL) and immediately covers the key constraints (wait time, job_id return). Every phrase earns its place; there is no filler or redundancy.

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 available output schema (not shown but indicated), the description provides sufficient context: it states the input format, the asynchronous wait, and the follow-up query action. It does not explicitly name the polling tool (e.g., xhs_get_video_speech_text_job), but the existence of such a sibling and the mention of 'next query action' make the workflow clear. Minor gaps like error handling or idempotency advice are not critical given the annotations.

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 coverage is 100%, so the parameter note_url is fully documented. The tool description repeats the same input formats (link, short link, share text) without adding new syntax details. With schema doing the heavy lifting, a 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 action (submit a video speech-to-text task), the resource (Xiaohongshu video note via URL, short link, or share text), and distinguishes it from the sibling by_note_id variant. It also outlines the wait/response behavior, leaving no ambiguity about the tool's purpose.

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 clear context (it is a submission task triggered by a note URL), but it does not explicitly state when to prefer this over the by_note_id sibling or exclude other tools. However, the naming and input type make the usage context obvious enough for an agent to infer the appropriate choice.

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

All SocialDataX 小红书 Xiaohongshu XHS RedNote 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?