Skip to main content
Glama

get-bilibili-rank

get-bilibili-rank

Retrieve Bilibili video rankings across categories like animation, music, and gaming to analyze current youth content trends.

Instructions

获取哔哩哔哩视频排行榜,包含全站、动画、音乐、游戏等多个分区的热门视频,反映当下年轻人的内容消费趋势

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what data is retrieved (Bilibili video rankings across sections) and hints at its cultural relevance, but lacks critical details: whether it's a read-only operation, any rate limits, authentication requirements, pagination behavior, or what the return format looks like (especially since there's no output schema). For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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 description is appropriately concise—one sentence that efficiently states the core functionality (getting Bilibili rankings) and adds context about section diversity and cultural relevance. It's front-loaded with the main purpose, though the second clause about 'reflecting youth trends' could be seen as slightly extraneous but still adds value. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a ranking tool with one parameter but no schema documentation), no annotations, and no output schema, the description is incomplete. It covers the 'what' (Bilibili video rankings) but misses the 'how': parameter usage, return format, behavioral constraints (e.g., is it safe to call frequently?), and differentiation from sibling tools. For a tool in a server with many similar trending/ranking tools, more contextual guidance is needed.

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

Parameters2/5

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

The input schema has one parameter ('type') with 0% description coverage (no schema documentation). The tool description provides no information about parameters—it doesn't mention the 'type' parameter at all, nor explain what values it accepts (e.g., whether it corresponds to the mentioned sections like '动画' or '音乐'). With low schema coverage and no compensation in the description, users are left guessing about parameter usage.

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?

The description clearly states the tool's purpose: '获取哔哩哔哩视频排行榜' (get Bilibili video rankings) with specific resources mentioned (全站、动画、音乐、游戏等多个分区的热门视频 - popular videos from various sections like all-site, animation, music, games). It distinguishes from siblings by focusing on Bilibili rankings rather than other platforms like Douban, Weibo, or news sources. However, it doesn't explicitly contrast with similar ranking tools (e.g., get-douban-rank) beyond the platform difference.

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 provides no guidance on when to use this tool versus alternatives. While it mentions '反映当下年轻人的内容消费趋势' (reflects current youth content consumption trends), this is more about the data's nature than usage context. There's no indication of when to choose this over other ranking/trending tools (e.g., get-douyin-trending for short videos, get-zhihu-trending for Q&A), nor any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xiaobenyang-com/1777316659328003'

If you have feedback or need assistance with the MCP directory API, please join our Discord server