bilibili MCP Server
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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_infoA | Get information about a Bilibili user |
| get_video_infoB | Get detailed information about a Bilibili video |
| search_videosB | Search for videos on Bilibili |
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 3 tools
Each tool has a clearly distinct purpose targeting different resources: user information, video information, and video search. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun pattern (get_user_info, get_video_info, search_videos) with clear, descriptive names that align well with their functions.
With only 3 tools, the server feels thin for a Bilibili platform that likely has more capabilities (e.g., comments, playlists, subscriptions). While the tools cover basic operations, the count is borderline low for the domain's scope.
The toolset is severely incomplete for a Bilibili server, missing essential CRUD operations like creating or updating content, managing interactions (e.g., comments, likes), and accessing user-specific features (e.g., subscriptions, history). This will cause significant agent failures in broader workflows.