Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bilibili_ranking

Fetch the current Bilibili all-site video ranking in rank order, including views, likes, creator details, and metadata for tracking trending videos.

Instructions

Get the current Bilibili all-site ranking. Returns the current Bilibili all-site video ranking in rank order. Each video has its rank, aid, title, url, cover, views, danmaku, replies, favorites, likes, duration_seconds, published_at, category and creator (name, mid, followers). Takes no parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

B3.4/5.0
Behavior3/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 disclose that the call is parameterless and enumerates the returned fields. However, it says nothing about freshness/caching, rate limits, or the read-only nature beyond the implied 'Get', so behavioral context is only partial.

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?

Purpose is front-loaded in the first sentence, then return shape and the no-parameter fact. The field enumeration is long but earns its place because no output schema exists. Slight redundancy between the first and second sentences.

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?

No output schema exists, so listing the returned fields (rank, aid, title, views, creator, etc.) usefully compensates. The one real gap is absent routing guidance against the many other Bilibili sibling tools; otherwise complete for a simple read-only endpoint.

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?

There are zero parameters and the description explicitly confirms 'Takes no parameters', matching the empty schema. Baseline for a 0-param tool with no schema nuance to add.

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 the current Bilibili all-site ranking') with a distinguishing scope modifier ('all-site'), which separates it from siblings like bilibili_popular, bilibili_weekly and bilibili_must_watch. It never names an alternative explicitly, so it stops short of a 5.

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 gives no when-to-use guidance and does not reference the other Bilibili sibling endpoints (popular, weekly, must_watch, vertical_home), so an agent must infer the choice on its own. It only implies usage by stating what the ranking is.

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