bili-material-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only Bilibili material source. Outputs are compact plain text with an approximate token count at the end. When you need several videos, pick them from search results first and read them together with ONE get_video_digests call (up to 5) instead of separate get_video_digest calls. Page through long subtitles with get_subtitle(offset=next_offset) only when needed.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_videosA | Search Bilibili videos. Returns one line per video: bvid | title | uploader | play/like/comment counts | duration | publish date. limit is capped at 20. order: totalrank (default), click, pubdate, dm (danmaku), stow (favorites), scores (comments). |
| get_video_digestA | Digest of ONE video (for several videos use get_video_digests): metadata and stats, compressed subtitle (timestamps removed, lines merged; first subtitle_max_chars characters), and the top hot comments sorted by likes. bvid may be a BV id or a video URL. If the subtitle is truncated, the output gives next_offset for get_subtitle. |
| get_video_digestsA | Batch digest: metadata, the FULL compressed subtitle (default, up to 20000 chars per video) and top hot comments for up to 5 videos in ONE call, so no follow-up get_subtitle call is needed. Prefer this over calling get_video_digest repeatedly — each extra tool step resends the whole conversation. To only skim videos before choosing, pass a small subtitle_max_chars (e.g. 500). subtitle_max_chars and top_comments apply per video. A video that fails is reported in its own section without aborting the rest. Reading 5 videos can take about 30 seconds because requests are throttled. |
| get_subtitleA | 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. |
| get_hot_commentsA | Top comments of a video sorted by likes, with emote codes, duplicates and very short comments removed. limit is capped at 50. Anonymous access only returns a few comments. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
get_video_digest and get_video_digests differ only by a plural 's' and perform near-identical work at different scales, which is a classic misselection trap despite the descriptions explaining the batch preference. The digest tools also overlap with get_subtitle and get_hot_comments, since the digest already embeds a compressed subtitle and top comments; the descriptions do clarify when to use each, but boundaries are softer than ideal.
All names are snake_case with a predictable verb_noun shape (search_videos, get_subtitle, get_hot_comments). The only blemish is the singular/plural pair get_video_digest / get_video_digests, which is consistent in form but makes the two names visually confusable.
Five tools is a tight, well-scoped set for fetching Bilibili video material, with each tool mapping to a concrete retrieval need. It is on the lean side, but nothing feels padded or redundant enough to warrant a lower score.
The surface covers search, single and batch digest, chunked subtitle reading, and comment retrieval, which are the core read workflows for video material collection. Gaps exist around uploader/author lookup, related or recommended videos, and paged search results beyond the 20-item cap, but these are workaroundable rather than blocking.