Skip to main content
Glama

SocialDataX B站 Bilibili MCP

bilibili_get_content_comments_by_id

Read-only

根据 Bilibili 内容 ID 获取视频、专栏或动态的一级评论列表。

Input Schema

NameRequiredDescriptionDefault
sort_typeNo评论排序方式:hot=最热,time_descending=最新。默认 hot。hot
content_idYesBilibili 内容 ID;用于获取一级评论。视频优先传 bvid(BV...);如果只有视频 aid,建议传 av{aid}(如 av116668525186915)以明确表示视频评论区;不建议直接传裸数字 aid,因为裸数字也可能是专栏/动态评论区 ID。专栏可传 cv 专栏 ID(如 cv9689859),动态/opus 可传 /opus/{id} 或 /dynamic/{id} 路径中的数字 post_id。不要传 comment_object_id、comment_id、链接或分享文案。
page_tokenNoBilibili 一级评论分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一内容、同一排序和同一入口的评论分页链路;content_id 入口 / by_id 工具返回的 token 只能继续用于 content_id 入口 / by_id 工具,url 入口 / by_url 工具返回的 token 只能继续用于 url 入口 / by_url 工具;不能跨能力、入口、内容或排序复用。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页内容评论列表。
pointsYes本次成功调用的积分消耗与账户积分余额。
comment_countYes平台返回的评论总数,通常包含一级评论和回复;不是当前页数量,也不等于 items 中一级评论条数;不可用时为 null。
next_page_tokenYes下一页不透明分页令牌;为空表示没有更多一级评论。继续获取一级评论下一页时,必须将返回的完整 next_page_token 原样作为 page_token 传回,并沿用本次调用入口;content_id 入口 / by_id 工具返回的 token 只能继续用于 content_id 入口 / by_id 工具,url 入口 / by_url 工具返回的 token 只能继续用于 url 入口 / by_url 工具。不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容;不能跨能力、入口、内容或排序复用。

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. Changed20 schema fields changed
    • addedOutput schema / properties / comment_count / title
      Added value: +"Comment Count"
    • addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / items / items / properties / author / properties / member_level / title
      Added value: +"Member Level"
    • 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: +"BilibiliCommentAuthorData"
    • addedOutput schema / properties / items / items / properties / comment_id / title
      Added value: +"Comment Id"
    • addedOutput schema / properties / items / items / properties / comment_object_id / title
      Added value: +"Comment Object Id"
    • addedOutput schema / properties / items / items / properties / comment_object_type / title
      Added value: +"Comment Object Type"
    • addedOutput schema / properties / items / items / properties / content / title
      Added value: +"Content"
    • addedOutput schema / properties / items / items / properties / image_urls / title
      Added value: +"Image Urls"
    • addedOutput schema / properties / items / items / properties / ip_location / title
      Added value: +"Ip Location"
    • 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 / reply_count / title
      Added value: +"Reply Count"
    • addedOutput schema / properties / items / items / title
      Added value: +"BilibiliContentCommentItemData"
    • 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: +"BilibiliContentCommentsResult"
  4. First observed

TDQS

A3.6/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 is covered. The description adds the meaningful scope detail that only first-level comments are returned (replies require a different tool), but says nothing about rate limits, auth requirements, or ordering behavior beyond the schema's sort_type enum.

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?

A single front-loaded sentence with no filler; the resource, retrieval key, and scope all appear before any qualifying clause. Nothing needs trimming.

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?

With an output schema present, return values need no explanation, and the schema fully covers pagination and ID formats. The remaining gap is that the description never explains when to prefer this tool over bilibili_get_content_comments_by_url, a distinction the agent must infer 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%, so the schema already documents content_id formats, sort_type, and the page_token contract in detail. The description contributes no parameter meaning beyond what the schema provides, which is the correct baseline of 3 when structured data does the heavy lifting.

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 pairs a specific verb ('获取') with a specific resource ('一级评论列表') and explicitly scopes it to three content types (视频、专栏、动态) retrieved by content ID. It also signals that only top-level comments are returned, which separates it from the replies sibling, though it never names that sibling 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?

The description implies when to use it — when you hold a Bilibili content ID rather than a URL — but never states this contrast, even though a by_url sibling exists. The routing guidance and token-reuse rules live only in the parameter descriptions, so the description body itself leaves the when-to-use choice to inference.

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