Skip to main content
Glama
Sign In
BusyBee MCP

BusyBee MCP

by danfeistar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_trending

Retrieve current hot and trending lists from supported platforms such as Douyin for topic selection and trend tracking. Configure platform and result limit per request.

Instructions

拉平台热搜/热榜（目前支持抖音）。适合做选题和热点追踪。

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": "get_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
platformNodouyin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/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 full burden. It does disclose a genuine behavioral constraint — only Douyin is supported today — which is valuable. But it says nothing about rate limits, whether results are cached/sampled, ordering, or how many items come back.

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?

Two short sentences, capability first and use case second, with no filler. Nothing to trim and nothing buried.

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

Completeness3/5

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

This is a simple read with zero required params and no output schema, so the burden is light. Still, an agent gets no hint of the return shape (a ranked list of hot topics?) or size, and no guidance beyond the single platform constraint.

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?

Schema description coverage is 0%, so the description must compensate. '目前支持抖音' partially clarifies the platform parameter's only valid value, but the limit parameter (default 20) and its bounds are entirely undocumented, leaving half the surface unexplained.

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+resource: fetch platform trending/hot lists (拉平台热搜/热榜). It also scopes availability ('目前支持抖音'), which no sibling shares. It does not explicitly name sibling tools, but the resource is distinct enough from search_posts/get_comments that confusion is unlikely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase '适合做选题和热点追踪' gives an implied usage context (content ideation, trend tracking) but no concrete when-to-use/when-not guidance and no alternative tools are referenced, e.g. list_platforms for discovering supported platforms.

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