Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bilibili_must_watch

Retrieve Bilibili's curated must-watch video collection, split into classic and latest videos with counts, plus title, subtitle, and explanation.

Instructions

Get Bilibili's curated must-watch videos. Returns Bilibili's curated must-watch collection, split into classic_videos and latest_videos with their counts, plus the collection title, subtitle and explanation. Each video has bvid, aid, title, url, cover, uploader, published, stats and achievement. Takes no parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bilibili_must_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral-disclosure burden. "Get" and "Returns" imply a read-only operation, and the return structure is described in detail, but auth requirements, rate limits, freshness, and error behavior are not addressed.

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?

The description is front-loaded with purpose and then gives return details. Since there is no output schema, the field enumeration earns its place, and the final no-parameters note is brief.

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?

Given the empty input schema and no output schema, the description does a good job explaining what the tool returns, including the collection metadata and per-video fields. It could be more complete by noting how this feed differs from other Bilibili feeds or how fresh the curated collection is.

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?

The tool has zero parameters, so the baseline is 4. The description confirms "Takes no parameters," which is redundant with the empty input schema but harmless.

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 Bilibili's curated must-watch videos." The return split into `classic_videos` and `latest_videos` further clarifies the resource, but the description never contrasts this with sibling Bilibili feeds such as `bilibili_popular`, `bilibili_ranking`, or `bilibili_weekly`.

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 explicit when-to-use or when-not-to-use guidance. With many sibling Bilibili feed tools, an agent must infer from the phrase "curated must-watch" alone that this is the right tool rather than `bilibili_popular` or `bilibili_weekly`.

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