polylens-bilibili

Overview Schema Source Related Servers Discussions Admin

get_feed

Read-only

Retrieve Bilibili homepage recommendation feed, up to 30 items per batch, and use a required jq expression to filter, shape, or extract fields from the returned video data.

Instructions

B 站首页推荐流，每批最多 30 条。

(homepage feed, recommendations, browse)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`jq`	Yes	必填的 jq 表达式。输入是全部条目组成的数组，每条字段：title,url,author,author_url,published_at,duration_sec,view_count,danmaku_count,like_count,rcmd_reason。体积大、多数任务用不到的字段：url（后续调用其他工具时需要）、author_url（查看 UP 主时需要）；特定任务需要时照常使用。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。

Output Schema

TableJSON Schema

Name	Required	Description	Default
`feed`	Yes
`count`	Yes
`jq_count`	No
`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 表达式。输入是全部条目组成的数组，每条字段：title,url,author,author_url,published_at,duration_sec,view_count,danmaku_count,like_count,rcmd_reason。体积大、多数任务用不到的字段：url（后续调用其他工具时需要）、author_url（查看 UP 主时需要）；特定任务需要时照常使用。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。",
+  "title": "Jq",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "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

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description's added value is the 'max 30 per batch' volume constraint. It does not say whether the feed is personalized, whether results refresh between calls, or what pagination behavior exists, so it is only a modest addition over 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?

One short sentence in Chinese plus a keyword line; the resource and its volume limit are front-loaded with zero filler. Every element earns its place.

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?

With an output schema present, return values need no explanation, and the input schema fully documents jq. What is missing is routing context: how this feed relates to keyword search or per-UP listing, and whether the 30-item cap can be extended. Adequate but with a real usage gap.

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% — the jq parameter is documented at length in the schema itself (input array, per-item fields, return-encoding rules, jq_count). The description adds nothing about the parameter, so the baseline 3 applies.

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

Purpose4/5

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

States a specific resource and verb-equivalent: the Bilibili homepage recommendation feed, with an explicit batch cap of 30 items. That is enough to distinguish it from search_videos, get_video_info or list_up_videos, though it never names those siblings as alternatives.

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?

The parenthetical keywords (homepage feed, recommendations, browse) hint at the browse use case but give no when-to-use/when-not guidance. Nothing tells the agent to prefer this over search_videos or list_up_videos for discovery.

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

Deploy Server