Skip to main content
Glama

SocialDataX B站 Bilibili MCP

bilibili_get_user_posted_videos_by_user_id

Read-only

根据 Bilibili 用户 user_id 获取公开发布视频列表。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesB 站用户 user_id,通常是 space.bilibili.com/{user_id} 路径里的数字 ID;可从搜索、详情、评论或用户资料结果中的 author.user_id 或 user_id 复制;不要传用户主页链接,不要传视频链接、昵称、BV 号或 aid。已有用户主页链接时使用 by_profile_url 工具。
sort_typeNo用户发布视频排序方式:time_descending=最新发布,view_count_descending=最多播放,collect_count_descending=最多收藏。默认 time_descending。time_descending
page_tokenNoBilibili 用户发布视频列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一用户和同一排序方式的视频列表分页链路,不能跨能力、用户或排序复用。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页用户发布视频列表。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
next_page_tokenYes下一页不透明分页令牌;为空表示没有更多用户发布视频。继续获取下一页时,必须将返回的完整 next_page_token 原样作为 page_token 传回;只能用于同一用户和同一排序方式的视频列表分页链路。不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容;不能跨能力、用户或排序复用。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark this read-only, and the description adds meaningful behavioral details: it retrieves only publicly posted videos, and the page_token description discloses that pagination tokens are opaque, must be passed unchanged, and are scoped to the same user and sort type. It does not cover rate limits or error behavior, but those are secondary for a read-only list retrieval.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The top-level description is a crisp single sentence, and parameter docs are detailed and logically organized. The page_token description is slightly redundant in its list of forbidden transformations, but every sentence serves a purpose in protecting the opaque-token contract.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the readOnlyHint/openWorldHint annotations and an output schema, the description plus parameter docs cover what the tool does, when to use it, how to paginate, and how to sort. Nothing essential for correct selection and invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the descriptions go far beyond basic schemas: user_id identifies exact sources and forbidden values, sort_type defines each enum option, and page_token details the opaque-token contract with explicit prohibitions and reuse restrictions. This materially helps the agent invoke the tool correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb (获取) and resource (公开发布视频列表) scoped by user_id, and the tool name reinforces that this is the user_id-based variant among sibling by_profile_url tools. It tells an agent exactly what it retrieves: a user's publicly posted Bilibili videos.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The user_id parameter description explicitly says to use by_profile_url when the agent already has a user homepage link, providing a direct routing rule to a sibling tool. It also enumerates forbidden inputs (links, nickname, BV, aid) and tells where to obtain a valid user_id, which is strong guidance for selecting and using this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources