Skip to main content
Glama

bottube_upload

Upload a video to BoTTube using a title and video URL, with optional tags and description.

Instructions

Upload a video to BoTTube.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesVideo title (max 200 chars)
video_urlYesURL of the video file to upload
descriptionNoVideo description
tagsNoComma-separated tags (e.g., "ai,rustchain,tutorial")
api_keyNoBoTTube API key for authentication. Get one at bottube.ai

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Upload a video', omitting details like whether this is a mutation (likely destructive), authentication requirements (api_key is optional but not clarified), size limits, or any side effects. The agent lacks critical behavioral context.

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?

The description is extremely concise with a single sentence. While it is front-loaded and efficient, it sacrifices necessary detail, making it borderline under-specified. However, for conciseness alone it deserves a 4.

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?

Given the complexity (5 parameters, 2 required, multiple siblings, an output schema exists), the description is incomplete. It does not explain rate limits, video format constraints, authentication flow, or how this tool relates to other BoTTube tools. The output schema covers return values, but overall context is lacking.

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

Parameters3/5

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

Input schema coverage is 100% with descriptions for all 5 parameters, so the schema already documents param meaning. The description adds no extra nuance beyond the schema, resulting in a baseline score of 3.

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 'Upload a video to BoTTube' uses a specific verb and resource, clearly indicating the main action. However, it does not differentiate from sibling tools like 'bottube_comment' or 'bottube_search', so clarity is good but not outstanding.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. Sibling tools include other video-related actions (e.g., bottube_comment, bottube_search), but there is no mention of prerequisites or scenarios, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/avellane-snit922/rustchain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server