clear_bilibili_cache
Clears cached Bilibili video data to free up memory and ensure fresh retrieval of trending content.
Instructions
清除B站视频数据缓存
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Clears cached Bilibili video data to free up memory and ensure fresh retrieval of trending content.
清除B站视频数据缓存
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 'clear cache' without detailing whether data is permanently deleted, whether user settings are affected, whether the action is reversible, or if any confirmation is required. This is a significant gap for a potentially destructive operation.
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 that directly communicates the tool's purpose without any redundant or filler content. It is perfectly sized for its trivial parameter structure.
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 the absence of annotations and an output schema, the description should compensate by explaining the implications of clearing the cache (e.g., data loss, scope, reversibility). It currently only states the action, which is insufficient for an agent to fully understand the consequences and safe usage of a destructive tool.
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?
The tool has zero parameters, so the input schema fully documents everything. The description correctly adds no parameter details, and the baseline score of 4 applies since there is nothing additional to explain.
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 action (清除 = clear) and the target (B站视频数据缓存 = Bilibili video data cache), distinguishing it from sibling search and hot-list tools as well as the analogous clear_baidu_cache tool.
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 is provided on when to use this tool versus alternatives like clear_baidu_cache, nor any prerequisites, situations where it should be avoided, or expected side effects. The description is purely functional without contextual usage advice.
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/WilliamQAQ0v0/hot-content-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server