Skip to main content
Glama
Sign In
Kdenlive MCP Server

Kdenlive MCP Server

by Va1bhav512
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bin_move_clip

Move a video clip to a specified folder in the project bin, or to the root when no folder is given, to keep assets organized.

Instructions

Move clip to folder (or root if folder None).

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": {
      "clip_id": "<clip_id>"
    },
    "name": "bin_move_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNo
clip_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are present, so the description carries the transparency burden. It does disclose the root-if-None behavior beyond the schema, and 'move' implies removal from the source location. It does not mention failure modes, permissions, or whether the target folder must already exist.

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?

A single, front-loaded sentence with no wasted words. The conditional root behavior is packed into a short parenthetical, preserving both clarity and brevity.

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?

For a simple two-parameter tool with an output schema, the description is mostly adequate. The main gap is the underspecified folder parameter, which could lead an agent to pass the wrong value type. The description could be complete with one more clause about folder format or validation.

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 description coverage is 0%, so the description must compensate. It adds meaning by clarifying that folder=None targets the root, which the anyOf schema does not convey. However, it leaves clip_id and the expected format of the folder parameter (ID vs name, existing folder) unexplained.

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 names a specific verb ('Move'), a resource ('clip'), and a destination ('folder' or root). It is unambiguous as a bin operation, though it does not explicitly contrast with sibling tools like timeline_move_clip.

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 action itself implies when to use it, but there is no explicit guidance about alternatives or non-use cases. The parenthetical 'or root if folder None' is more about parameter behavior than usage context.

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