Skip to main content
Glama

SocialDataX B站 Bilibili MCP

bilibili_get_content_likes_and_reposts_by_url

Read-only

根据 Bilibili 专栏/动态链接、移动端链接、b23.tv 短链接或分享文案获取赞与转发列表。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "bilibili_get_content_likes_and_reposts_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesBilibili 专栏/动态链接、移动端链接、t.bilibili.com 动态链接、b23.tv 短链接或包含链接的分享文案;支持 /opus/{id}、/dynamic/{id}、t.bilibili.com/{id}、t.bilibili.com/h5/dynamic/detail/{id} 等同一专栏/动态的常见 B 站链接形态。从专栏搜索结果出发时,先获取详情,再使用详情里的 post.share_url 或 post.post_id。不要传视频链接、其他链接或用户主页链接。
page_tokenNoBilibili 专栏/动态赞与转发列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一专栏/动态的同一 post_id 或同一 url 赞与转发分页链路;继续翻页时必须使用同一个入口,by_post_id 返回的 token 只能继续传给 by_post_id,by_url 返回的 token 只能继续传给 by_url;不能跨能力或内容复用。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页赞与转发动作记录列表,每项包含动作类型、B 站展示文案、补充说明和互动用户。
pointsYes本次成功调用的积分消耗与账户积分余额。
post_idYes本次赞与转发列表对应的专栏/动态 post_id;可用于后续不带当前 page_token 的新查询。继续当前分页时必须沿用原入口和 next_page_token,不要用本字段切换入口。不是评论 ID、用户 ID 或 cv 专栏 ID。
next_page_tokenYes下一页不透明分页令牌;为空表示没有更多结果。继续获取赞与转发下一页时,必须将返回的完整 next_page_token 原样作为 page_token 传回,并沿用本次调用入口;by_post_id 返回的 token 只能继续传给 by_post_id,by_url 返回的 token 只能继续传给 by_url。不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容;不能跨能力、入口或专栏/动态复用。
like_repost_countYes赞与转发合计总数,不是当前页数量;当前不区分赞和转发分别计数;不可用时为 null。

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. Changed14 schema fields changed
    • addedOutput schema / properties / items / items / properties / action_text / title
      Added value: +"Action Text"
    • addedOutput schema / properties / items / items / properties / action_type / title
      Added value: +"Action Type"
    • addedOutput schema / properties / items / items / properties / description / title
      Added value: +"Description"
    • addedOutput schema / properties / items / items / properties / user / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / items / items / properties / user / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / items / items / properties / user / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / items / items / properties / user / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / items / items / properties / user / title
      Added value: +"BilibiliAuthorData"
    • addedOutput schema / properties / items / items / title
      Added value: +"BilibiliContentLikeRepostItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / like_repost_count / title
      Added value: +"Like Repost Count"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / properties / post_id / title
      Added value: +"Post Id"
    • addedOutput schema / title
      Added value: +"BilibiliContentLikeRepostsResult"
  4. First observed

TDQS

B3.4/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 safety and external-access behavior are covered structurally, and an output schema exists for return values. The description adds modest scope context by naming the content types (专栏/动态), which implies videos and user profiles are out of scope, but it says nothing about result ordering, list size, or whether pagination is required to see the full list.

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?

A single front-loaded sentence with no filler; every word carries content and the input enumeration is compact. It is perhaps over-compressed relative to the routing nuance the tool actually needs, but there is no wasted text.

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?

Given a simple two-parameter read-only tool with a rich schema and an output schema, the description covers the core purpose adequately and need not explain return values. However, for a paginated open-world fetch, the description omits how this differs from the by_post_id variant and that the operation is paginated, leaving routing to the agent's inference from the tool name.

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 url and page_token descriptions are extremely detailed (accepted link shapes, token opacity, chain-matching rules). The one-line description adds essentially no parameter meaning beyond the schema, so the baseline 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 (fetch the likes-and-reposts list) and enumerates the accepted input forms (column/dynamic links, mobile links, b23.tv short links, share text). It implicitly separates itself from the _by_post_id sibling by being URL-driven, but never names that alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: 'given one of these Bilibili post links, get its likes and reposts.' The genuinely useful routing rules (do not pass video links or profile links; when starting from article search, first fetch detail then use post.share_url or post.post_id) live entirely in the url parameter schema, not in the description. There is no explicit when-to-use-this-vs-by_post_id guidance at the description level.

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