SocialDataX B站 Bilibili MCP

bilibili_get_user_info_by_profile_url

Read-only

根据 B 站用户主页链接、短链接或分享文案获取用户资料；不要传视频链接。如果上一步结果已返回 user_id，可直接使用 user_id 入口。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`profile_url`	Yes	B 站用户主页链接、短链接或分享文案；不要传 user_id，不要传视频链接、BV 号或 aid；已有 user_id 时使用 by_user_id 工具。

Output Schema

TableJSON Schema

Name	Required	Description
`bio`	Yes	用户简介；不可用时为空字符串。
`name`	Yes	B 站用户名称；不可用时为空字符串。
`gender`	Yes	用户性别：male 表示男，female 表示女，unknown 表示未知或未公开。
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`user_id`	Yes	B 站用户 user_id；用于标识作者或用户。
`birthday`	Yes	公开生日，通常为 MM-DD；不可用时为 null。
`verified`	Yes	是否有 B 站个人或机构认证。
`live_info`	Yes	用户直播状态摘要；没有直播间或不可用时为 null。
`avatar_url`	Yes	用户头像链接；不可用时为 null。
`profile_url`	Yes	B 站用户主页链接；可用于打开用户主页；不可用时为 null。
`charging_url`	Yes	充电入口链接；不可用时为 null。
`charging_count`	Yes	累计充电人数；未开通或不可用时为 null。
`follower_count`	Yes	粉丝数；不可用时为 null。
`profile_notice`	Yes	B 站空间公告；没有公告或不可用时为 null。
`following_count`	Yes	关注数；不可用时为 null。
`video_view_count`	Yes	累计视频播放数；不可用时为 null。
`posted_audio_count`	Yes	用户公开投稿音频数量；不可用时为 null。
`posted_video_count`	Yes	用户公开投稿视频数量；不可用时为 null。
`verification_label`	Yes	B 站认证说明；没有认证或不可用时为 null。
`received_like_count`	Yes	累计获赞数；不可用时为 null。
`posted_content_count`	Yes	用户公开投稿总数，对应 B 站空间投稿页的「投稿」总数；不可用时为 null。
`posted_image_text_count`	Yes	用户公开投稿图文数量，对应 B 站空间投稿页的「图文」分类；不可用时为 null。

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.3/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. The description adds useful input-format context (short links and share text accepted, video links rejected) but does not disclose additional behavioral traits such as rate limits or parsing edge cases. This is adequate but not exceptional.

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

Conciseness5/5

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

Two sentences with no fluff. The core purpose is stated first, followed by the key exclusions and a routing hint. Every sentence earns its place and the structure is easy to scan.

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?

For a single-parameter read-only tool with a fully documented schema and an output schema present, the description is complete. It tells the agent what to pass, what not to pass, and when to prefer the alternative user_id entry, leaving no critical gap.

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 single parameter's description already explains accepted formats and exclusions. The tool description mostly repeats this information, adding no new semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the action ('获取用户资料' / get user info) and the specific resource (user profile URL, short link, or share text), and it explicitly excludes video links. It differentiates from the sibling by_user_id and content-specific tools by focusing on profile-based user info.

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 description gives clear when-to-use and when-not-to-use guidance: do not pass video links, and if an earlier step already returned user_id, use the user_id entry instead. The schema reinforces this by naming the by_user_id tool directly, so an agent can route correctly.

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

All SocialDataX B站 Bilibili MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?