哔哩哔哩
bilibiliRetrieve Bilibili hot video rankings. Configure limit and cache settings to fetch current trending content.
Instructions
获取哔哩哔哩热门视频排行榜
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| noCache | No |
bilibiliRetrieve Bilibili hot video rankings. Configure limit and cache settings to fetch current trending content.
获取哔哩哔哩热门视频排行榜
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| noCache | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only states the purpose; no mention of caching behavior, rate limits, or side effects. The 'noCache' parameter hints at caching but is unexplained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, but it lacks important structure and detail. While not verbose, it fails to provide valuable information beyond the tool's basic purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, no annotations, and sparse parameter info, the description is severely incomplete. It does not explain the return format, pagination, or ranking criteria, making it insufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description should explain parameters. It does not mention 'limit' or 'noCache' at all, leaving their semantics entirely to the schema names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool gets Bilibili's hot video ranking (specific verb and resource). It distinguishes from siblings by naming the platform, though it does not elaborate on what makes this ranking unique.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus other ranking tools (e.g., weibo, douyin). Lacks any context about preferred scenarios or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/FrankXMX/dailyhotmcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server