Skip to main content
Glama
wecandeo

@wecandeo/mcp-videopack-v4

Official
by wecandeo

wecandeo_video_modify_folder

Move a video to a different media-archive folder by providing the video access key and target folder ID.

Instructions

Move a video to a different media-archive folder.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderIdYesTarget media-archive folder ID
accessKeyYesOriginal video access key (Level 1)
Behavior2/5

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

The description only says 'Move' without disclosing behavioral details such as whether the operation is a move or copy, permissions required, or side effects. With no annotations, the burden is on the description.

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 a single, clear sentence with no wasted words. However, it could be expanded to include behavioral context without losing conciseness.

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 no annotations, no output schema, and only 2 parameters, the description is too minimal. It fails to explain the full effect (move vs copy) or provide return value hints, leaving gaps for correct tool invocation.

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 coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 ('Move a video') and the resource ('different media-archive folder'), distinguishing it from sibling tools like 'wecandeo_video_modify_meta' or 'wecandeo_video_add_to_package'.

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 is provided on when to use this tool (e.g., prerequisites like video must be in a folder) or when to avoid it. Alternatives are not mentioned.

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