Skip to main content
Glama

SocialDataX B站 Bilibili MCP

bilibili_get_user_posted_articles_by_user_id

Read-only

根据 Bilibili 用户 user_id 获取公开发布单篇专栏列表。

Input 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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed10 schema fields changed
    • addedOutput schema / properties / article_count / title
      Added value: +"Article Count"
    • addedOutput schema / properties / items / items / properties / cover_image_url / title
      Added value: +"Cover Image Url"
    • addedOutput schema / properties / items / items / properties / description / title
      Added value: +"Description"
    • addedOutput schema / properties / items / items / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / items / items / properties / post_id / title
      Added value: +"Post Id"
    • addedOutput schema / properties / items / items / properties / share_url / title
      Added value: +"Share Url"
    • addedOutput schema / properties / items / items / title
      Added value: +"BilibiliUserPostedArticleData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / title
      Added value: +"BilibiliUserPostedArticlesResult"
  4. 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 and openWorldHint=true, so the safety profile is covered by structured data. The description adds the useful scope constraint 公开发布 (publicly posted), implying non-public or restricted content is excluded, but it says nothing about result ordering, pagination behavior, or empty-result cases. With annotations already covering safety, this is an acceptable but thin contribution.

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 well-formed sentence that front-loads the user scope and the resource type, with no redundant or filler wording. It is efficient, although its brevity is also the reason it lacks usage guidance.

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

Completeness3/5

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

An output schema exists and the input schema is fully documented, so return values and parameter mechanics need not be restated. However, the description does not do enough to help the caller choose between this tool and its many siblings, particularly the by_profile_url variant, on which the caller must rely instead. For a list tool with many sibling tools, that routing gap keeps completeness at the minimum viable level.

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%, and the schema already explains user_id, how to source it, and the strict opaque-token rules for page_token. The description adds no parameter meaning beyond what the schema provides, so the baseline of 3 applies.

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 and resource (获取…单篇专栏列表) scoped to a Bilibili user identified by user_id, which is enough to distinguish it from the by_profile_url scope in its name. It does not explicitly contrast itself with the sibling tools for dynamics or videos, so differentiation relies on the tool name rather than the description text.

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 offers no when-to-use or when-not-to-use guidance and never names an alternative. A user with a profile URL instead of a numeric ID could most easily pick this tool by mistake, so the caller must note that routing hint from the schema instead of the description.

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