Skip to main content
Glama
bili-material-mcp
by sac432

get_subtitle

Read-onlyIdempotent

Retrieve a Bilibili video's compressed subtitles in chunks by starting at offset 0 and passing the returned next_offset to continue, with page selection for multi-part videos.

Instructions

Read the compressed subtitle of a video in chunks. Start with offset=0 and pass the returned next_offset to continue. page selects the part of a multi-part video. Requires login.

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": {
      "bvid": "<bvid>"
    },
    "name": "get_subtitle"
  }
}

Input Schema

NameRequiredDescriptionDefault
bvidYes
pageNo
offsetNo
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: an authentication requirement ('Requires login'), chunked/truncated return content ('compressed subtitle'), and the continuation contract (returned next_offset), which matters because there is no output schema.

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?

Three short sentences, each earning its place: what it does, how to iterate it, and the login prerequisite. The most important operational fact (start at offset=0) is front-loaded.

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 no output schema, the description correctly discloses the returned next_offset and the login requirement, which are the two things an agent cannot infer from structured fields. It stops short of saying what happens when a video has no subtitle or how 'compressed' content differs from raw text, but nothing essential to a correct first call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and largely meets it: offset is explained with its starting value and continuation semantics, page is tied to multi-part videos, and max_chars is implied by 'in chunks'. Only bvid is left implicit ('of a video'), which is a minor gap rather than a blocking one.

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?

States a specific verb and resource: 'Read the compressed subtitle of a video in chunks.' That is clearly distinct from the sibling tools (comments, digests, search), though it never names an alternative or states a boundary against them.

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?

Gives procedural guidance — start at offset=0, pass the returned next_offset, use page for multi-part videos, and login is required — but this is how-to-call guidance rather than when-to-use-this-versus-something-else guidance. An agent knows how to page through it but not when it should prefer this over get_video_digest.

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