Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bilibili_weekly

Fetch a Bilibili weekly selected-video issue by number, or omit the number to get the latest. Returns issue metadata and each video's title, uploader, duration, and stats.

Instructions

Get a Bilibili weekly selected-video issue. Returns one issue of Bilibili's weekly selected-video series: number (1 to 1000000) picks the issue, and omitting it returns the latest. The issue has subject, label, description and reminder, and each video has bvid, title, uploader, duration_seconds, recommendation and stats_text. An unknown issue number returns 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberNoPositive issue number; omit for the latest issue

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does well: it enumerates the returned issue and video fields and discloses error behavior ('an unknown issue number returns 404'). It omits auth, rate-limit, and pagination details, but 404 handling and the return shape are the key traits for a read-only lookup.

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?

Front-loads the purpose, then parameter behavior, then return shape and error. The sentence is dense and runs long, but every clause (range, latest-default, field list, 404) earns its place, especially since no output schema exists.

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 a single-optional-parameter read tool with no annotations or output schema, the description compensates well by documenting parameter behavior, the full return payload, and the failure case. Only minor gaps (pagination, why the upper bound is 1000000) remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3), and the description adds meaningful detail beyond the schema by stating the valid range ('1 to 1000000') and confirming that omitting the value returns the latest issue.

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 verb and resource ('Get a Bilibili weekly selected-video issue') and pins the scope to a numbered issue of the weekly series, which is distinct from the popular/ranking/must-watch siblings. It never names a sibling for comparison, so it stops short of explicit differentiation.

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 description explains the parameter's effect (omit for latest) but gives no when-to-use guidance and names no alternatives among the many bilibili_* siblings. An agent is left to infer that this is the weekly-issue lookup tool.

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