Skip to main content
Glama
Sign In
polylens-bilibili

polylens-bilibili

by liu-xindi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_subtitles

Read-only

Extract sentence-level subtitles from Bilibili videos using a URL or BV/av ID, with optional language and segment selection, to create transcripts and captions.

Instructions

逐句返回。字幕可能为 AI 生成或机器翻译，存在误差。

(subtitles, captions, transcript)

Input Schema

NameRequiredDescriptionDefault
jqYes必填的 jq 表达式。输入是全部条目组成的数组，每条字段：start,end,content。体积大、多数任务用不到的字段：start（需要定位时间时保留）、end；特定任务需要时照常使用。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。
langNo轨道语种，如 zh-CN、en-US、ai-zh。不传则取平台给的第一条。可选值见返回的 available_langs。
pageNo分段序号，1 起。不传时取链接里的 ?p=N，两者都没有则第 1 段。单段视频忽略此项。
videoYes视频链接、b23.tv 短链，或裸 BV/av 号；含链接的分享文案也可直接传入。
descriptionYes格式为 工具名:目的。

Output Schema

NameRequiredDescriptionDefault
langNo
countYes
jq_countNo
video_idYes
elapsed_sNo
subtitlesYes
available_langsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.12.1
    • addedInput schema / properties / description
      Added value: +{
+  "description": "格式为 工具名:目的。",
+  "title": "Description",
+  "type": "string"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "description": "视频链接、b23.tv 短链，或裸 BV/av 号；含链接的分享文案也可直接传入。",
-  "title": "Url",
-  "type": "string"
-}
    • addedInput schema / properties / video
      Added value: +{
+  "description": "视频链接、b23.tv 短链，或裸 BV/av 号；含链接的分享文案也可直接传入。",
+  "title": "Video",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "url",
-  "jq"
-]New value: +[
+  "description",
+  "video",
+  "jq"
+]
  2. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / jq
      Added value: +{
+  "description": "必填的 jq 表达式。输入是全部条目组成的数组，每条字段：start,end,content。体积大、多数任务用不到的字段：start（需要定位时间时保留）、end；特定任务需要时照常使用。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。",
+  "title": "Jq",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "jq"
+]
    • addedOutput schema / properties / jq_count
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Jq Count"
+}
  3. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a real reliability caveat (subtitles may be AI-generated or machine-translated and contain errors) and states sentence-level granularity, but says nothing about auth needs, rate limits, or pagination behavior for a multi-page resource.

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?

Two short sentences plus a keyword line with no filler, and the return-granularity statement is front-loaded. The parenthetical keyword line is mildly redundant with the tool name but earns its place as a search/disambiguation aid.

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

Completeness3/5

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

An output schema exists, so return values need not be re-explained, and the accuracy caveat covers the main quality risk. Still, for a 5-parameter tool with pagination and language selection, the absence of any when-to-use or alternative-routing content leaves a clear gap.

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 jq/lang/page/video parameters are documented in detail within the schema itself. The description contributes no additional parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The bilingual keyword line "(subtitles, captions, transcript)" identifies the resource, and "逐句返回" indicates sentence-level return granularity. However, the opening line describes output shape rather than stating a verb+resource purpose, and it draws no distinction from siblings like get_danmaku_counts or get_parts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, nor on prerequisites such as login state or which lang track to prefer (deferred entirely to the linked available_langs). The AI-generation/translation caveat is a data-quality note, not usage guidance.

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

Deploy Server

Other Tools