Bilibili-Api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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_infoC | Get information about a Bilibili user |
| get_video_infoC | Get detailed information about a Bilibili video |
| search_videosC | 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: get_user_info targets user data, get_video_info targets video metadata, and search_videos targets video discovery. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tools follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes and snake_case formatting. This predictable naming scheme enhances readability and usability across the set.
With only 3 tools, the set feels thin for a Bilibili API server, which might be expected to handle more operations like comments, playlists, or uploads. However, it covers basic user, video, and search functions adequately for a minimal scope.
The tools provide read-only access to users, videos, and search, but lack CRUD operations (e.g., no create, update, or delete) or broader API coverage like comments or subscriptions. This limits agents to informational tasks without full lifecycle management.