SocialDataX B站 Bilibili MCP

bilibili_search_articles

Read-only

搜索 Bilibili 专栏文章。用户需要按搜索词查找专栏时使用；已有视频、专栏或动态链接，或已有内容 ID 时使用对应的统一详情或评论工具；支持 page_token 翻页、排序和分区筛选。

Input Schema

Name	Required	Description	Default
`keyword`	Yes	搜索 Bilibili 专栏文章的搜索词，可传关键词或短语，例如品牌名、话题、人物名或产品名；不要传视频链接、专栏/动态链接、用户主页链接、BV 号、aid、专栏/动态 ID 或 page_token。
`category`	No	专栏分区筛选：all=全部分区，animation=动画，gaming=游戏，film_and_tv=影视，lifestyle=生活，hobbies=兴趣，light_novel=轻小说，technology=科技，notes=笔记。	all
`sort_type`	No	专栏排序方式：general=综合排序，time_descending=最新发布，view_count_descending=最多点击/阅读，like_count_descending=最多喜欢，comment_count_descending=最多评论。	general
`page_token`	No	Bilibili 专栏搜索分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一关键词、排序方式和分区筛选的专栏搜索链路，不能跨能力、关键词或筛选条件复用。消费多页搜索结果时，建议按 content_id 作为稳定键合并结果。

Output Schema

Name	Required	Description
`items`	Yes	当前页专栏搜索结果。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`next_page_token`	Yes	下一页不透明分页令牌；为空表示没有更多专栏搜索结果。继续获取专栏搜索下一页时，必须将返回的完整 next_page_token 原样作为 page_token 传回；只能用于同一关键词、排序方式和分区筛选的专栏搜索链路；消费多页搜索结果时，建议按 content_id 作为稳定键合并结果。不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容；不能跨能力、关键词或筛选条件复用。

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
```
Changed20 schema fields changedNov 3, 2026
- addedOutput schema / properties / items / items / properties / author / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / items / items / properties / author / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / items / items / properties / author / title
```
Added value: +"BilibiliArticleSearchAuthorData"
```
- addedOutput schema / properties / items / items / properties / category_id / title
```
Added value: +"Category Id"
```
- addedOutput schema / properties / items / items / properties / category_name / title
```
Added value: +"Category Name"
```
- addedOutput schema / properties / items / items / properties / comment_count / title
```
Added value: +"Comment Count"
```
- addedOutput schema / properties / items / items / properties / content_id / title
```
Added value: +"Content Id"
```
- 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 / image_urls / title
```
Added value: +"Image Urls"
```
- addedOutput schema / properties / items / items / properties / like_count / title
```
Added value: +"Like Count"
```
- addedOutput schema / properties / items / items / properties / publish_time / title
```
Added value: +"Publish Time"
```
- addedOutput schema / properties / items / items / properties / share_url / title
```
Added value: +"Share Url"
```
- addedOutput schema / properties / items / items / properties / title / title
```
Added value: +"Title"
```
- addedOutput schema / properties / items / items / properties / view_count / title
```
Added value: +"View Count"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"BilibiliArticleSearchItemData"
```
- 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: +"BilibiliArticleSearchResult"
```
First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that paging, sorting, and category filtering are supported, but it does not mention rate limits, result size, or anything beyond the annotations and schema. A 3 is appropriate when the annotations carry the behavioral burden.

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?

Three compact clauses, front-loaded with the action and resource, then usage routing, then capability summary. It is efficient overall, though the final capability clause largely duplicates what the schema already declares.

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?

The tool is a paginated search, and the description covers the action, when to use it, the alternatives, and the supported filtering and paging. An output schema exists, and the schema fully documents the parameters, so nothing an agent needs to call it correctly 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%, and the schema already documents keyword, category enums, sort_type enums, and page_token semantics in detail. The description only restates the capabilities ('支持 page_token 翻页、排序和分区筛选') without adding syntax or constraints beyond the schema, so the baseline of 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?

The description states a specific verb and resource: '搜索 Bilibili 专栏文章'. The resource name ('专栏文章') alone separates it from bilibili_search_videos and bilibili_search_users, and the second clause separates it from the detail and comment tools that work from links or IDs.

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?

It gives both when to use this tool ('用户需要按搜索词查找专栏时使用') and when not to use it: if you already have a video, article, or dynamic link, or a content ID, use the corresponding detail or comment tool instead. No sibling routing is left to inference.

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?