polylens-bilibili

Overview Schema Source Related Servers Discussions Admin

get_parts

Read-only

Extract Bilibili video parts and pages from a URL, BV/av ID, or share text, then filter results with a required jq expression.

Instructions

即分 P。单段视频返回一项。(video parts, pages)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`jq`	Yes	必填的 jq 表达式。输入是全部条目组成的数组，每条字段：page,part,duration。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。
`url`	Yes	视频链接、b23.tv 短链，或裸 BV/av 号；含链接的分享文案也可直接传入。

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`parts`	Yes
`jq_count`	No
`video_id`	Yes
`elapsed_s`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.1Oct 7, 2026

addedInput schema / properties / jq

Added value: +{
+  "description": "必填的 jq 表达式。输入是全部条目组成的数组，每条字段：page,part,duration。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。",
+  "title": "Jq",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "jq"
+]

addedOutput schema / properties / jq_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Jq Count"
+}

First observedv0.1.0Oct 5, 2026

TDQS

C2.8/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 and scope are covered. The description adds one genuine behavioral fact beyond that, namely that a single-segment video yields a single item, which helps set expectations about result cardinality. It stops there, disclosing nothing about rate limits, auth needs, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is very short and has no wasted words, but it reads as two disconnected fragments rather than a front-loaded informative sentence. It is concise to the point of under-specification rather than efficient communication.

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?

An output schema exists and the parameter schema is fully documented, so the description is not obligated to explain return values or parameter formats. However, for a 2-required-param tool in a crowded sibling set, the lack of any routing guidance leaves a real gap that the structured fields cannot fill.

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% and both parameters (url, jq) are documented in detail in the schema, including the array shape and field names (page, part, duration). The description adds no parameter-level information beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (分P / video parts / pages) but largely restates the tool name rather than naming an action with scope. The English gloss '(video parts, pages)' helps clarify the domain, and '单段视频返回一项' hints at output cardinality, but it never says explicitly what is fetched or how it differs from get_video_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as get_video_info, get_danmaku, or get_subtitles, all of which are plausible siblings an agent could confuse with this one. The agent must infer usage purely from the tool name.

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

Deploy Server