Skip to main content
Glama
polylens-bilibili

polylens-bilibili

by liu-xindi

list_up_videos

Read-only

Retrieve a Bilibili uploader’s videos to browse channel content, filter by keyword, sort by newest or popularity, and paginate results with a jq expression.

Instructions

每批最多 40 条。total 是视频总数,带 keyword 时为匹配数。

(uploader videos, channel uploads, other videos by this author)

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": {
      "description": "<description>",
      "author_url": "<author_url>",
      "jq": "<jq>"
    },
    "name": "list_up_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqYes必填的 jq 表达式。输入是本批条目组成的数组,每条字段:title,url,published_at,duration_sec,view_count,danmaku_count,comment_count。分页字段不在输入里;只筛本批,筛完为空时仍以 has_more 判断有无下一批。结果为字符串时原样返回,其他结果编码为表格或 JSON;结果为数组时 jq_count 是其长度。
orderNo排序。newest
cursorNo续取游标:不传从头开始,回传上次返回的 next_cursor 取下一批。
keywordNo按关键词筛选投稿,平台除标题外也会匹配简介等。
author_urlYesUP 主空间链接(其他工具返回的 author_url),或数字 mid。
descriptionYes格式为 工具名:目的。

Output Schema

NameRequiredDescriptionDefault
countYes
totalYes
authorYes
videosYes
has_moreYes
jq_countNo
elapsed_sNo
author_urlYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.1
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "格式为 工具名:目的。",
      +  "title": "Description",
      +  "type": "string"
      +}
    • changedInput schema / properties / jq / description
      Previous value: -"必填的 jq 表达式。输入是本批条目组成的数组,每条字段:title,url,published_at,duration_sec,view_count,danmaku_count,comment_count。体积大、多数任务用不到的字段:url(后续调用其他工具时需要);特定任务需要时照常使用。分页字段不在输入里;只筛本批,筛完为空时仍以 has_more 判断有无下一批。结果为字符串时原样返回,其他结果编码为表格或 JSON;结果为数组时 jq_count 是其长度。"New value: +"必填的 jq 表达式。输入是本批条目组成的数组,每条字段:title,url,published_at,duration_sec,view_count,danmaku_count,comment_count。分页字段不在输入里;只筛本批,筛完为空时仍以 has_more 判断有无下一批。结果为字符串时原样返回,其他结果编码为表格或 JSON;结果为数组时 jq_count 是其长度。"
    • changedInput schema / required
      Previous value: -[
      -  "author_url",
      -  "jq"
      -]New value: +[
      +  "description",
      +  "author_url",
      +  "jq"
      +]
  2. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / jq
      Added value: +{
      +  "description": "必填的 jq 表达式。输入是本批条目组成的数组,每条字段:title,url,published_at,duration_sec,view_count,danmaku_count,comment_count。体积大、多数任务用不到的字段:url(后续调用其他工具时需要);特定任务需要时照常使用。分页字段不在输入里;只筛本批,筛完为空时仍以 has_more 判断有无下一批。结果为字符串时原样返回,其他结果编码为表格或 JSON;结果为数组时 jq_count 是其长度。",
      +  "title": "Jq",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "author_url"
      -]New value: +[
      +  "author_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

B3.3/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, so the description doesn't need to restate safety. It adds useful pagination behavior: max 40 items per batch, and total semantics where keyword changes total to the matching count. It still omits auth/rate-limit details, but the added pagination context is meaningful.

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?

The definition is very concise and every sentence carries useful information. Its structure could be better front-loaded, since the purpose appears in a trailing English parenthetical after pagination details, but there is no filler or repetition.

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 schema coverage is complete, so return values and most parameter details need not be described. Still, for a six-parameter list tool with several sibling listing/search tools, the description is minimally adequate and lacks clear routing guidance for when to choose it over alternatives.

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 schema already documents all six parameters. The description adds output-related meaning for keyword ('total is matching count when keyword is present') but does not meaningfully extend parameter syntax or semantics beyond the schema.

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 parenthetical names the resource scope ('uploader videos, channel uploads, other videos by this author'), and the batch/total text implies a listing operation. However, there is no explicit verb phrase such as 'List videos for a given author,' and it does not clearly differentiate itself from siblings like search_videos or get_up_info.

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 scope phrase implies this tool is for an author's uploads, giving an implicit use context. But it gives no explicit when-to-use guidance, prerequisites, or comparison to alternatives such as search_videos, get_feed, or get_up_info.

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