Skip to main content
Glama
bili-material-mcp
by sac432

get_hot_comments

Read-onlyIdempotent

Retrieve the top comments for a Bilibili video, sorted by likes and filtered for emote codes, duplicates, and very short comments; limit results up to 50.

Instructions

Top comments of a video sorted by likes, with emote codes, duplicates and very short comments removed. limit is capped at 50. Anonymous access only returns a few comments.

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": {
      "bvid": "<bvid>"
    },
    "name": "get_hot_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
bvidYes
limitNo
max_chars_per_commentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds real behavioral detail beyond them: the result set is not raw top-N by likes because emotes, duplicates and short comments are dropped, the limit is hard-capped at 50, and anonymous access degrades results. It does not disclose the returned fields, which is the remaining gap.

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?

Three short sentences, front-loaded with what the tool returns, followed by the two constraints that change agent behavior (limit cap, anonymous degradation). No filler or restated name.

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?

There is no output schema, and the description gives only partial return-shape information (comments carry emote codes, ranked by likes) without saying what fields come back or how many comments anonymous access yields. Combined with the undocumented max_chars_per_comment, an agent has enough to call it but not enough to fully predict the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it only covers one of three: the limit cap of 50. bvid is left to inference and max_chars_per_comment is never mentioned, leaving ambiguous whether it truncates comment text or interacts with the 'very short comments removed' filter.

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 resource (top comments of a video) plus the ranking criterion (sorted by likes) and the filtering applied (emote codes, duplicates, very short comments removed). No sibling could be confused with this: get_subtitle, get_video_digest and search_videos operate on entirely different resources.

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 implied by the resource description (fetch ranked comments for one video) and it adds a useful constraint about anonymous access returning few results, but it never names an alternative tool or states when an agent should prefer something else. No exclusions are given.

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