bilibili-info-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SESSDATA | No | Bilibili login cookie. Required only for fetching subtitles. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-bilibili-video-infoA | Fetches Bilibili video metadata (title, author, duration, description, publish date, view count) and subtitles/captions. |
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 1 tool
With only one tool, there is zero ambiguity or potential for misselection. The tool's purpose is fully unique by default.
A single descriptive tool name using a get-<resource>-info pattern. Consistency is trivial but the style is clear and predictable.
One tool feels thin for a video platform server, but it is compact and focused on the 'info' scope. It sits at the low end of the borderline range.
The tool covers metadata and subtitles for a known video, but there is no discovery (search/list/trending) or related operations (comments, chapters). This leaves an agent stranded without a video ID.