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

get_video_digest

Read-onlyIdempotent

Retrieve a compact digest for one Bilibili video, including metadata and stats, a compressed subtitle excerpt, and top liked comments; accept a BV ID or video URL.

Instructions

Digest of ONE video (for several videos use get_video_digests): metadata and stats, compressed subtitle (timestamps removed, lines merged; first subtitle_max_chars characters), and the top hot comments sorted by likes. bvid may be a BV id or a video URL. If the subtitle is truncated, the output gives next_offset for get_subtitle.

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_video_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
bvidYes
top_commentsNo
subtitle_max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses subtitle compression behavior (timestamps removed, lines merged), truncation and next_offset, and comment sorting by likes. It does not describe pagination or rate limits, but the main behavioral traits an agent needs are covered.

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?

The description is compact and front-loads the core purpose before listing output contents. The long parenthetical and run-on sentence make it slightly dense, but every clause carries useful 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?

With no output schema, the description adequately summarizes the return payload and the next_offset continuation mechanism. The main remaining gap is that top_comments is not explicitly described as controlling how many comments are returned.

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 0%, so the description must carry parameter meaning. It explains bvid accepts a BV id or URL and that subtitle_max_chars limits the returned subtitle prefix, but top_comments is only indirectly implied by 'top hot comments sorted by likes' and its count semantics are not stated.

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 ('Digest of ONE video') and immediately distinguishes it from the multi-video sibling get_video_digests. It also names the constituent content: metadata and stats, compressed subtitle, and top hot comments.

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 explicitly says to use get_video_digests for several videos and points to get_subtitle when the subtitle is truncated via next_offset. The conditions that select alternatives are stated directly rather than left to inference.

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