Skip to main content
Glama
Sign In
polylens-bilibili

polylens-bilibili

by liu-xindi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_parts

Read-only

Fetch the parts (pages) of Bilibili videos from links or BV/av IDs, grouping segments per video and using a jq expression to format the output.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
jqYes必填的 jq 表达式。输入是单个视频的分段组成的数组，每条字段：page,part,duration。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。
videosYes视频列表，每项为链接、b23.tv 短链或裸 BV/av 号。
descriptionYes格式为 工具名:目的。

Output Schema

NameRequiredDescriptionDefault
resultsYes
elapsed_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.12.1
    • addedInput schema / properties / description
      Added value: +{
+  "description": "格式为 工具名:目的。",
+  "title": "Description",
+  "type": "string"
+}
    • changedInput schema / properties / jq / description
      Previous value: -"必填的 jq 表达式。输入是全部条目组成的数组，每条字段：page,part,duration。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。"New value: +"必填的 jq 表达式。输入是单个视频的分段组成的数组，每条字段：page,part,duration。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。"
    • removedInput schema / properties / url
      Removed value: -{
-  "description": "视频链接、b23.tv 短链，或裸 BV/av 号；含链接的分享文案也可直接传入。",
-  "title": "Url",
-  "type": "string"
-}
    • addedInput schema / properties / videos
      Added value: +{
+  "description": "视频列表，每项为链接、b23.tv 短链或裸 BV/av 号。",
+  "items": {
+    "type": "string"
+  },
+  "title": "Videos",
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "url",
-  "jq"
-]New value: +[
+  "description",
+  "videos",
+  "jq"
+]
    • addedOutput schema / $defs
      Added value: +{
+  "PartsItem": {
+    "properties": {
+      "count": {
+        "default": 0,
+        "title": "Count",
+        "type": "integer"
+      },
+      "error": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Error"
+      },
+      "input": {
+        "title": "Input",
+        "type": "string"
+      },
+      "jq_count": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Jq Count"
+      },
+      "parts": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Parts"
+      }
+    },
+    "required": [
+      "input"
+    ],
+    "title": "PartsItem",
+    "type": "object"
+  }
+}
    • removedOutput schema / properties / count
      Removed value: -{
-  "title": "Count",
-  "type": "integer"
-}
    • removedOutput schema / properties / jq_count
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Jq Count"
-}
    • removedOutput schema / properties / parts
      Removed value: -{
-  "title": "Parts",
-  "type": "string"
-}
    • addedOutput schema / properties / results
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/PartsItem"
+  },
+  "title": "Results",
+  "type": "array"
+}
    • removedOutput schema / properties / video_id
      Removed value: -{
-  "title": "Video Id",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "video_id",
-  "count",
-  "parts"
-]New value: +[
+  "results"
+]
  2. Changed3 schema fields changedv0.3.1
    • 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"
+}
  3. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the grouping behavior ('one group per video, one item for a single-segment video'), which is minor and partly duplicated by the output schema. No auth, rate-limit, or ordering behavior 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.

Conciseness3/5

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

It is very short, but the telegraphic bilingual phrasing ('即分 P', '每个视频一组') and the parenthetical mash of Chinese and English gloss make it feel under-specified rather than tight. The key idea is front-loaded, but readability suffers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool requires three parameters, including an unusual 'description' field whose required format ('工具名:目的') and the mandatory jq expression are never explained in the description. With an output schema present, returns are covered, but the description leaves the agent without guidance on these non-obvious required inputs.

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 all three parameters (including the detailed jq expression semantics) are documented in the schema itself. The description adds no meaning beyond that, which meets the baseline 3 for fully documented schemas.

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 gloss '(video parts, pages)' conveys that this retrieves a video's multi-part (分P) segments, grouping them per video. However, the phrasing is telegraphic with no clear verb, and it never states what the tool actually does in a sentence an agent can act on. It distinguishes it loosely from siblings like get_video_info, but only by inference.

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 statement of when to use this tool versus alternatives such as get_video_info or get_subtitles. The description merely describes the return shape ('one group per video'), leaving the agent to guess the selection context.

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