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

get_video_digests

Read-onlyIdempotent

Batch-fetch metadata, subtitles, and hot comments for up to 5 videos in one call, avoiding repeated tool steps and saving processing time.

Instructions

Batch digest: metadata, the FULL compressed subtitle (default, up to 20000 chars per video) and top hot comments for up to 5 videos in ONE call, so no follow-up get_subtitle call is needed. Prefer this over calling get_video_digest repeatedly — each extra tool step resends the whole conversation. To only skim videos before choosing, pass a small subtitle_max_chars (e.g. 500). subtitle_max_chars and top_comments apply per video. A video that fails is reported in its own section without aborting the rest. Reading 5 videos can take about 30 seconds because requests are throttled.

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": {
      "bvids": "<bvids>"
    },
    "name": "get_video_digests"
  }
}

Input Schema

NameRequiredDescriptionDefault
bvidsYes
top_commentsNo
subtitle_max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already carry read-only/idempotent/non-destructive, so the bar is lower, yet the description adds real behavior: 20000-char default subtitle cap, 5-video limit, per-video scoping of options, per-video failure isolation without aborting the batch, and ~30s latency from throttling. What remains unstated is pagination/return shape detail, but the per-section failure behavior is the key operational fact and it is disclosed.

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?

Front-loaded with the core value proposition and the sibling comparison, and nearly every sentence carries decision-relevant information. Slightly dense with nested parentheticals, but no filler.

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?

No output schema exists, and the description still explains what comes back (metadata, subtitle, top hot comments, per-video failure sections) plus the latency expectation. That is enough for an agent to call it correctly and to budget time for a 5-video batch.

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

Parameters4/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 compensate, and it does for two of three params: subtitle_max_chars (default 20000 per video, use ~500 to skim) and top_comments (applied per video, default 20 from schema). bvids is only weakly explained — the name implies video IDs but the expected ID format and the 5-item ceiling per call could be stated against the parameter.

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 verb and resource: a batch digest returning metadata, the full compressed subtitle, and top hot comments for up to 5 videos in one call. It distinguishes itself from both get_video_digest (repeated calls) and get_subtitle (no follow-up needed), so an agent can select it without inspecting either schema.

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?

Explicitly says to prefer this over calling get_video_digest repeatedly and explains why (each extra tool step resends the whole conversation). It also gives a concrete alternative mode: pass a small subtitle_max_chars (~500) to skim before choosing.

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