Skip to main content
Glama
7oMB2006

Bilibili Video Research

by 7oMB2006
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Research a Bilibili Video

analyze_bilibili_video
Read-only

Resolve public Bilibili video URLs to analyze content, metadata, and community context. Choose language, vision, or multimodal modes to answer research questions with evidence.

Instructions

Resolves a public Bilibili URL, always returns public metadata and an explicit community-context status, and optionally samples 20 most-liked root comments while displaying only 3 hot comments plus up to 2 distinct high-signal comments. Supports language-only, visual-only, and multimodal research.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic Bilibili video URL, including b23.tv short URLs.
modeYeslanguage: captions then audio only; vision: silent video only; multimodal: original video with both channels.
questionYesThe research question.
end_secondsNoOptional source-video interval end in seconds. Provide together with start_seconds.
media_detailNoUse low for a broad long-video pass and default for close inspection.default
start_secondsNoOptional source-video interval start in seconds. Provide together with end_seconds.
source_qualityNoOptional source acquisition quality. It affects Bilibili downloads, not local-video tools.
include_commentsNoInclude untrusted community context. Fetches at most 20 most-liked root comments, presents only 3-5 representative comments, and reports empty or fetch-failed status explicitly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / source_quality
      Added value: +{
+  "description": "Optional source acquisition quality. It affects Bilibili downloads, not local-video tools.",
+  "properties": {
+    "fps": {
+      "anyOf": [
+        {
+          "const": 30,
+          "type": "number"
+        },
+        {
+          "const": 60,
+          "type": "number"
+        }
+      ],
+      "description": "Target source-video frame rate. Overrides the profile preset."
+    },
+    "on_unavailable": {
+      "default": "error",
+      "description": "error refuses an unavailable target instead of silently downgrading; warn allows a reported fallback.",
+      "enum": [
+        "error",
+        "warn"
+      ],
+      "type": "string"
+    },
+    "profile": {
+      "default": "standard",
+      "description": "standard targets 1080p30; high targets 1440p30; custom requires explicit resolution and fps.",
+      "enum": [
+        "standard",
+        "high",
+        "custom"
+      ],
+      "type": "string"
+    },
+    "resolution": {
+      "description": "Target source-video resolution. Overrides the profile preset.",
+      "enum": [
+        "720p",
+        "1080p",
+        "1440p",
+        "2160p"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / end_seconds
      Added value: +{
+  "description": "Optional source-video interval end in seconds. Provide together with start_seconds.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • changedInput schema / properties / include_comments / description
      Previous value: -"Attach untrusted community context. Fetches at most 20 most-liked root comments but presents only 3-5 representative comments."New value: +"Include untrusted community context. Fetches at most 20 most-liked root comments, presents only 3-5 representative comments, and reports empty or fetch-failed status explicitly."
    • addedInput schema / properties / start_seconds
      Added value: +{
+  "description": "Optional source-video interval start in seconds. Provide together with end_seconds.",
+  "minimum": 0,
+  "type": "number"
+}
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

The annotation readOnlyHint=true already establishes safety, and the description adds substantial behavioral detail: it always returns an explicit status, samples at most 20 root comments, displays only 3 hot comments plus up to 2 high-signal comments, and supports three modes. No contradiction with the annotations.

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?

Two dense sentences with no filler: it front-loads the core resolve-and-return behavior, then the optional comment behavior, then the mode support. Every clause carries operational information and earns its place.

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?

For an 8-parameter tool with no output schema, the description names the key return categories and comment-count policy, which is helpful. It does not detail the metadata/status response structure or the implications of source_quality, but the input schema covers parameter semantics thoroughly, so the description is mostly complete for selection and invocation.

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 baseline is 3. The description adds some high-level output context, but the mode and comment-sampling details largely restate what is already in the schema. It does not add meaningful new meaning for parameters like start_seconds, end_seconds, media_detail, or source_quality.

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 action ('Resolves a public Bilibili URL') and a concrete resource, then explains what is returned: public metadata, explicit community-context status, and optional comment sampling. This clearly distinguishes the tool from the generic-looking siblings by tying it to Bilibili-specific analysis.

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 usage for public Bilibili URLs and mentions the three research modes, giving some context. However, it does not explicitly compare with analyze_video or inspect_video_window, nor does it state when to prefer language-only, vision-only, or multimodal research. The guidance is present but only implicit.

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

Deploy Server

Other Tools