Skip to main content
Glama
Sign In
BusyBee MCP

BusyBee MCP

by danfeistar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_creator_posts

Retrieve recent posts for a creator account using platform and handle or ID to review published content and activity.

Instructions

拉某个账号最近发布的作品列表。creator 填 handle 或平台 id。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>",
      "creator": "<creator>"
    },
    "name": "list_creator_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
creatorYes
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It conveys only that results are 'recently published' posts; nothing about ordering, pagination behavior, rate limits, or error behavior for an unknown creator is stated.

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?

Two short sentences with the core purpose front-loaded and the identifier note immediately after. No filler, though the brevity contributes to the specification gaps rather than offsetting them.

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?

With no annotations, no output schema, and 0% schema description coverage across three parameters, this description is too thin for the tool's surface. An agent still cannot determine valid platform values, page-size semantics, or what the returned list looks like.

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 document all three parameters. It usefully resolves the main ambiguity for 'creator' (handle or platform id), but leaves 'platform' with no indication of accepted values and 'limit' with no mention of its default of 20 or any cap.

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: listing an account's recently published posts, with the creator identifier clarified as handle or platform id. It is distinguishable from get_creator/get_post, but it never contrasts itself with the sibling search_posts, so the boundary is left implicit.

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?

Usage is implied — call this when you already know a creator and want their recent output. There is no explicit statement of when to prefer this over search_posts, or that search_creators/get_creator should be used first to resolve a handle or platform id.

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