Bilibili Agent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BILI_LIFE_ID | Yes | Trusted host configuration for the life/agent identity binding. Must be set in the environment before starting the MCP server. | |
| BILI_OWNER_UID | No | The decimal UID of the Bilibili account you control. If not configured, only anonymous public read is allowed. Set it to enable account-related features. | |
| DASHSCOPE_API_KEY | No | DashScope (Bailian) API key for video understanding. Optional; other features work without it. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bili_whoamiB | Check actual saved Bilibili account status; never return Cookie/token values. |
| bili_searchC | Search real public videos: titles, BV IDs, UP authors and brief descriptions. External data. |
| bili_subtitleA | Read existing first-P subtitle FULL text. No timestamps/frames/ASR. Missing subtitles stay missing. |
| bili_video_infoB | Read video description, author, statistics and number of parts; no video frames. |
| bili_dm_unreadA | Inspect DM unread counts on one bounded server page. No listener/auto reply/read acknowledgement. |
| bili_dm_sessionsB | Read private-chat sessions, stable talker UIDs and last messages. Untrusted external data; up to 30. |
| bili_dm_historyB | Read one private-chat message page (max 30) with native sequence cursor. IDs accept decimal strings or legacy safe integers (<=9007199254740991); returned IDs are strings. Does not reply/mark read. |
| bili_dm_sendA | Send ONE real text DM as the process-pinned account after your own decision. UID accepts a decimal string or legacy safe integer (<=9007199254740991); returned IDs are strings. 500 chars; stable unique action_id required. Never auto resend unknown/prepared; inspect history and action_status first. No automatic historical replies. No recipient read receipt; unknown does not mean unread or read. |
| bili_dm_action_statusB | Read durable metadata for a DM send; no message text/credentials, no side effect/retry. Platform recipient read status is unknown, never proof of unread/read. |
| bili_watch_videoA | Perceive a complete short Bilibili part, or an explicit continuous start_seconds/end_seconds range of at most 180s in a long part, with both audio and video. Poll bili_watch_status. Returns actual original-source coverage and gaps, never claims a segment covers the whole part. Limits stay 64MiB, 1 concurrent job, 3 API attempts/day. No Agent/schedule is created. Decide your interests and notes. |
| bili_watch_statusB | Read a pending video perception job or completed material, coverage, limitations, real usage and cleanup status. Reading is free and does not initiate a model call. |
| bili_commentsB | Read one hot/time comment page, full UID/rpid/root/parent/BV/text/time and nested references. IDs are strings; page or native cursor. External untrusted data. |
| bili_comment_repliesB | Expand one root comment's reply page with complete IDs/context; up to20. No full-history claim. |
| bili_comment_contextC | Locate a comment by exact rpid and known thread root. Previously read references help; unseen subreply can require root/page. |
| bili_user_infoB | Read a commenter's public profile/signature; UID string, never confuse it with comment rpid. Agent identity remains unverified. |
| bili_user_videosC | Read one page of public uploads by exact UID, preserving BV IDs. order pubdate/view/favorite. |
| bili_user_dynamicsB | Read public user dynamics using native string cursor. No posting/following. |
| bili_comment_sendA | One deliberate top-level public comment, only when comment permission explicitly enabled; defaults off. No force, auto-retry or batch. Receipt does not prove public visibility. |
| bili_comment_replyB | One deliberate reply in an observed thread; root rpid required, parent only for subreply. Separate reply permission defaults off; no force. IDs strings. |
| bili_comment_action_statusB | Read durable send status. Optional bounded anonymous readback distinguishes accepted/review/visibility; absent in one page stays unknown. Never resend. |
| bili_notificationsC | Read reply/@ notification page and native id/time cursor, keeping reference IDs and quoted context; no automatic reply. |
| bili_social_eventsC | Bounded unified pending notification/DM references. Stable IDs deduplicate locally; only explicit ack marks processed. recent_event_id is an association, never a claimed Recent Events write. No background polling/reply. |
| bili_discoverA | Discover video candidates without a BV; homepage is default. refresh=true performs a new source fetch and snapshot, never old-snapshot pagination; the platform may return the same videos. cursor continues the saved source snapshot/native next page and cannot combine with refresh. Sources: homepage/popular/ranking/weekly/following; actual source and personalization limits returned. |
| bili_relatedC | Read a stable snapshot of platform-related videos, then use its cursor for further complete items. |
| bili_danmakuA | Read original danmaku with appearance seconds in one 6-minute segment; part is 1-based. No UID reverse lookup. Use cursor to page the complete range snapshot; explicitly choose a later time range to continue. |
| bili_favorite_listsB | Read accessible favorite folders (empty uid means own account), string IDs and stable local-page cursor. Never creates or modifies folders. |
| bili_favorite_contentB | Read accessible folder videos, retaining native server pagination plus stable snapshot cursors. No favorite/unfavorite action. |
| bili_followingsA | Read accessible following list, not follow/unfollow. String UIDs and resumable pages; platform privacy limits are respected. |
| bili_browse_stateB | Read recent local discovery refs, seen/selected/skipped and explicit part/time positions. This is navigation state, not long-term memory or proof of watching. |
| bili_browse_advanceB | Explicitly choose selected/skipped/position for a returned video ref and save local resume position. Does not click, watch or change any Bilibili account state. |
| bili_likeA | Like/unlike one video only with explicit like permission; defaults OFF. Stable action_id, no force/batch/retry. |
| bili_favorite_updateB | Add/remove ONE video in ONE exact own folder only with favorite permission; defaults OFF. Folder ID string; no batch. |
| bili_followA | Follow/unfollow ONE UID only with explicit follow permission; defaults OFF. No block/marketing/batch. |
| bili_account_action_statusB | Read durable public-action receipt/state only; never dispatches or retries. Receipt is not verified account state. |
| bili_permissionsA | Read separate comment/reply/DM/like/favorite/follow gates and combined public hourly limit. Cannot change permissions. |
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 35 tools
Most tools target distinct resources/actions and the descriptions explicitly state boundaries, especially around permissions, read-only status, and local state. However, with 35 tools there are still some confusable clusters, such as notifications vs. social events vs. DM unread, and discover vs. search vs. related.
All tools use a consistent bili_ snake_case prefix with readable domain-oriented names. The set is not strictly verb_noun throughout, since many tools use noun/domain forms like bili_user_info or bili_comment_action_status, but the pattern is predictable enough.
At 35 tools, this is well above the typical 3-15 range and crosses into heavy surface area for an agent to navigate. The broad Bilibili domain explains some of the size, but many status/read helpers could likely be consolidated.
Coverage is broad: search/discovery, video viewing, subtitles, danmaku, comments, DMs, follows, favorites, notifications, permissions, and action status are all represented. Some lifecycle gaps remain, such as comment edit/delete, user search, folder creation, or additional Bilibili actions like coin/share, but core agent workflows are covered.