Skip to main content
Glama
wecandeo

@wecandeo/mcp-videopack-v4

Official
by wecandeo

wecandeo_upload_caption

Upload WebVTT caption files to videos. Specify access key, source path or URL, language, and caption type (standard or SDH).

Instructions

Upload a WebVTT (.vtt) caption file for a video. Issues a caption upload token for the accessKey then uploads. source can be a local file path or a remote URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langIdNoLanguage code ID from wecandeo_upload_caption_language
sourceYesLocal file path or remote URL of the .vtt caption file
accessKeyYesOriginal video access key (Level 1) to attach the caption to
captionTypeNoCaption type: STANDARD (default) or SDH (for the hearing impaired)
Behavior3/5

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

Discloses the two-step token issuance and source types, but lacks details on overwrite behavior, file size limits, or authentication requirements. No annotations to offset.

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 sentences are front-loaded with purpose and process details. Every phrase adds value.

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?

Given no output schema, the description explains the upload flow but omits return values, error handling, and whether captions replace or append. Adequate but not thorough.

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?

Schema descriptions cover all 4 parameters, so baseline 3 applies. The description adds minimal extra context beyond specifying source as local or remote URL.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (upload), the resource (WebVTT caption file for a video), and distinguishes from sibling tools like wecandeo_upload_video and wecandeo_video_caption.

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 versus alternatives. With siblings like wecandeo_video_caption available, the description should clarify use cases or prerequisites.

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/wecandeo/mcp-wecandeo-v4'

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