Skip to main content
Glama
Sign In
BusyBee MCP

BusyBee MCP

by danfeistar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_post

Retrieve details for a single social media post by platform and post ID, including TikTok or Douyin numeric video IDs, to inspect content and metadata.

Instructions

查单条内容的详情。post_id 填平台的内容 id；TikTok/抖音也可传视频链接里的数字 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>",
      "post_id": "<post_id>"
    },
    "name": "get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

As no annotations are present, the description carries the full burden of transparency. It provides behavioral context by clarifying that the post_id is flexible (content ID vs. video link number), which is a key operational constraint for the caller.

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?

The definition is extremely concise. It front-loads the main function and follows immediately with a parenthetical clarification detailing input variations, making it highly efficient.

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

Completeness4/5

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

For a basic GET request tool, the description is sufficiently complete. It provides the required action and the necessary constraints for the key parameters, allowing an agent to invoke it successfully without further information.

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

Parameters4/5

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

With 0% schema description coverage, the description must add substantial value. It achieves this by explicitly defining that the post_id can be sourced from two distinct formats: a platform ID or a numerical ID from a video link, which is not reflected in the simple schema.

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 purpose is to 'check the details of a single piece of content.' By specifying 'single piece of content,' it effectively distinguishes this tool from broader search or listing siblings like search_posts or list_creator_posts.

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 description provides crucial input guidelines by stating that the post_id can be either a platform's content ID or a numerical ID extracted from a video link. This operational detail helps the agent determine the appropriate input format.

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