Skip to main content
Glama

SocialDataX B站 Bilibili MCP

bilibili_get_user_posted_articles_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 工具。
page_tokenNoBilibili 用户发布单篇专栏分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一用户的单篇专栏列表分页链路,不能跨能力或用户复用。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, lowering the burden. The description adds useful scope details by specifying '公开发布' (publicly published) and '单篇专栏' (single-column articles), but it does not disclose pagination behavior or other traits beyond what the schema already covers. It meets the minimum but does not go further.

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 description is a single efficient sentence with no filler or duplication of schema content. It is adequately front-loaded with the core purpose.

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

Completeness4/5

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

Given that the tool has an output schema and annotations, the short description is sufficient for an agent to understand the core operation. Pagination details are present in the schema, and the returning list format is likely covered by the output schema, so no critical information is missing.

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

Parameters3/5

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

Schema description coverage is 100% with rich parameter descriptions for both user_id and page_token. The tool description adds no additional parameter nuance, so the baseline score of 3 applies per the high-coverage rule.

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

Purpose4/5

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

The description states a specific verb ('获取' / fetch) and a specific resource ('公开发布单篇专栏列表' / list of public single-column articles) keyed by user_id. It clearly distinguishes the tool from the by_profile_url variant, though it does not explicitly name that sibling.

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

Usage Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus alternatives such as bilibili_get_user_posted_articles_by_profile_url. The parameter schema mentions using by_profile_url when a profile URL is available, but that is not part of the tool description itself, leaving the agent without explicit when-to-use/when-not-to-use instructions.

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