SocialDataX B站 Bilibili MCP

bilibili_get_user_info_by_profile_url

Read-only

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

Input Schema

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

Output 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.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```

Changed22 schema fields changedNov 3, 2026

addedOutput schema / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
addedOutput schema / properties / bio / title
```
Added value: +"Bio"
```
addedOutput schema / properties / birthday / title
```
Added value: +"Birthday"
```
addedOutput schema / properties / charging_count / title
```
Added value: +"Charging Count"
```
addedOutput schema / properties / charging_url / title
```
Added value: +"Charging Url"
```
addedOutput schema / properties / follower_count / title
```
Added value: +"Follower Count"
```
addedOutput schema / properties / following_count / title
```
Added value: +"Following Count"
```
addedOutput schema / properties / gender / title
```
Added value: +"Gender"
```

changedOutput schema / properties / live_info / anyOf

Previous value: -[
-  {
-    "properties": {
-      "cover_image_url": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "直播间封面图链接；不可用时为 null。"
-      },
-      "is_live": {
-        "description": "直播间当前是否正在直播。",
-        "type": "boolean"
-      },
-      "live_url": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "直播间页面链接；不可用时为 null。"
-      },
-      "room_id": {
-        "description": "B 站直播间 ID。",
-        "type": "string"
-      },
-      "title": {
-        "description": "直播间标题；不可用时为空字符串。",
-        "type": "string"
-      }
-    },
-    "required": [
-      "room_id",
-      "is_live",
-      "title",
-      "live_url",
-      "cover_image_url"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "cover_image_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "直播间封面图链接；不可用时为 null。",
+        "title": "Cover Image Url"
+      },
+      "is_live": {
+        "description": "直播间当前是否正在直播。",
+        "title": "Is Live",
+        "type": "boolean"
+      },
+      "live_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "直播间页面链接；不可用时为 null。",
+        "title": "Live Url"
+      },
+      "room_id": {
+        "description": "B 站直播间 ID。",
+        "title": "Room Id",
+        "type": "string"
+      },
+      "title": {
+        "description": "直播间标题；不可用时为空字符串。",
+        "title": "Title",
+        "type": "string"
+      }
+    },
+    "required": [
+      "room_id",
+      "is_live",
+      "title",
+      "live_url",
+      "cover_image_url"
+    ],
+    "title": "BilibiliUserLiveInfoData",
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / name / title
```
Added value: +"Name"
```
addedOutput schema / properties / posted_audio_count / title
```
Added value: +"Posted Audio Count"
```
addedOutput schema / properties / posted_content_count / title
```
Added value: +"Posted Content Count"
```
addedOutput schema / properties / posted_image_text_count / title
```
Added value: +"Posted Image Text Count"
```
addedOutput schema / properties / posted_video_count / title
```
Added value: +"Posted Video Count"
```
addedOutput schema / properties / profile_notice / title
```
Added value: +"Profile Notice"
```
addedOutput schema / properties / profile_url / title
```
Added value: +"Profile Url"
```
addedOutput schema / properties / received_like_count / title
```
Added value: +"Received Like Count"
```
addedOutput schema / properties / user_id / title
```
Added value: +"User Id"
```
addedOutput schema / properties / verification_label / title
```
Added value: +"Verification Label"
```
addedOutput schema / properties / verified / title
```
Added value: +"Verified"
```
addedOutput schema / properties / video_view_count / title
```
Added value: +"Video View Count"
```
addedOutput schema / title
```
Added value: +"BilibiliUserInfoData"
```

First observedSep 1, 2026

TDQS

A4/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 the useful workflow trait that it can be chained after a step returning user_id, but says nothing about failure behavior for malformed share text or about rate limits on this external-facing read.

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 short sentences, no filler, with the input forms stated first and the sibling routing hint second. Nothing in it could be removed without losing routing information.

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?

The tool is a simple single-parameter read with an output schema, so return-value explanation is unnecessary, and the description covers accepted inputs, exclusions, and the fallback tool. Only the missing distinction from the by_profile_url content-listing siblings keeps it from a 5.

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 already enumerates the accepted formats and exclusions, so the description largely repeats the schema. It does reinforce the share-text form, but adds no format examples or parsing caveats beyond the structured field. Baseline 3 applies.

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?

States a specific verb plus resource ('获取用户资料') and the accepted identifier forms (homepage link, short link, share text), which distinguishes it from bilibili_get_user_info_by_user_id and from the by_profile_url content-listing siblings. The negative constraint ('不要传视频链接') further rules out the most likely confusion with the video-scoped tools.

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

Usage Guidelines4/5

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

Explicitly tells the agent when to use the alternative entry point ('如果上一步结果已返回 user_id，可直接使用 user_id 入口') and when not to use this tool (video links). It does not mention the posted-content siblings that also take a profile URL, but the routing guidance it does give is actionable.

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?