Skip to main content
Glama
liu-xindi

polylens-bilibili

by liu-xindi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_subtitles

Read-only

Retrieve sentence-level subtitles, captions, or transcripts from Bilibili videos by URL, BV/av ID, or share link. Choose language/page; login required.

Instructions

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

(subtitles, captions, transcript)

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo
countYes
jq_countNo
video_idYes
elapsed_sNo
subtitlesYes
available_langsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds meaningful context beyond them: an auth requirement and a data-quality caveat that subtitles may be AI-generated or machine-translated and thus error-prone. No format or pagination detail, but the added warnings are genuinely useful.

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?

Extremely terse and front-loads the return format, auth requirement, and quality caveat in three short lines with no filler. Slightly under-elaborated rather than verbose.

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 a full output schema and 100% parameter coverage, the description need only carry auth and caveats, which it does. The remaining gap is the absence of guidance on when to prefer this over related content tools.

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%, with jq, url, lang, and page each thoroughly documented in the schema (including the 逐句 output shape and available_langs). The description adds nothing about parameters, so the baseline 3 applies.

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

Purpose4/5

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

The name get_subtitles plus the parenthetical gloss (subtitles, captions, transcript) makes the resource unambiguous, and 逐句返回 specifies the return granularity. It is clear what the tool retrieves, though it lacks explicit differentiation from siblings like get_danmaku.

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?

It states a prerequisite (需要登录) but gives no when-to-use guidance or alternatives relative to sibling tools such as get_danmaku or get_video_info. Usage is only implied by the tool name and keywords.

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