SocialDataX B站 Bilibili MCP

bilibili_submit_video_speech_text_by_video_url

根据 Bilibili 视频链接、短链接或分享文案提交口播转文字任务；每次处理一个分 P，提交后最多等待 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": {
      "video_url": "<video_url>"
    },
    "name": "bilibili_submit_video_speech_text_by_video_url"
  }
}

Input Schema

Name	Required	Description	Default
`video_url`	Yes	Bilibili 视频链接、b23.tv 短链接或包含视频链接的分享文案；多 P 视频可在普通视频 URL 中使用 p 参数选择一个分 P，例如 ?p=2；普通视频链接未传 p 时转写 P1，短链接按解析后的目标分 P 转写；每次只转写一个分 P；不要传 BV 号或用户主页链接。

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.

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description discloses valuable async behavior: wait up to 240 seconds, and if incomplete return job_id plus a next-step query action. This goes beyond the annotations, which only signal non-readonly, non-idempotent behavior. It could be richer by naming the query tool or describing success responses, but the output schema covers some of that.

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 states the core action, then adds the per-part scope and the timeout/job_id behavior. Every clause earns its place and there is no redundant restatement of the tool name or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only one parameter, a well-detailed input schema, an output schema, and helpful annotations, the description covers what an agent needs: input types, per-part behavior, wait time, and fallback response with job_id. The 'next query action' is vague, but the sibling bilibili_get_video_speech_text_job makes the intended follow-up identifiable.

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% and the video_url parameter description already explains accepted URL forms, the p parameter behavior, and exclusions. The tool description largely restates rather than adds to this, so it does not need to compensate; 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 uses a specific verb ('submit') and resource ('speech-to-text task'), and clearly scopes the input to Bilibili video links, short links, or share text. It also adds the 'one sub-P per call' constraint, which distinguishes it from related submit/query siblings like bilibili_submit_video_speech_text_by_bvid.

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 gives clear input context: use URL/short-link/share-text, do not pass BV IDs or profile links, and one sub-P is processed at a time. It does not explicitly name the by-BV sibling as the alternative or name the follow-up query tool, so it falls short of fully explicit when-not/alternatives guidance.

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

All SocialDataX B站 Bilibili 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?