Kdenlive MCP Server

by Va1bhav512

Overview Schema Source Related Servers Discussions Admin

Python

Local

project_list_profiles

List all supported video output profiles (like hd1080p30, 4k60) to choose the right format for export or analysis.

Instructions

Enumerate all available video output profiles (hd1080p30, 4k60, sd_pal, etc.).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_list_profiles"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 3, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. 'Enumerate' strongly implies a read-only listing operation, and the examples give useful context about the kind of values returned. However, it does not explicitly state that the operation has no side effects, nor does it clarify whether 'available' is global or dependent on the current project context.

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 description is a single sentence that leads with the action and noun, then provides illustrative examples. There is no redundant information, and every word contributes to understanding the tool's purpose.

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

Completeness5/5

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

For a zero-parameter list operation with an output schema present, the description is complete. An agent can safely invoke the tool with no arguments and expect a list of available profile identifiers, as illustrated by the examples. Nothing critical is missing.

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?

The tool has zero parameters, so the parameter baseline is 4. The description is not required to explain parameters, but the examples add helpful context about the kind of output values the tool returns, which is a small bonus.

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 identifies the action (Enumerate) and resource (all available video output profiles), with concrete examples (hd1080p30, 4k60, sd_pal). It effectively conveys what the tool returns, though it does not explicitly distinguish itself from similar sibling tools like project_get_render_profiles or project_get_profile.

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

Usage Guidelines4/5

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

The phrase 'all available video output profiles' provides clear context for when to use the tool: when an agent needs to discover available output profiles. It does not explicitly mention alternatives or exclusions, but the intent is evident enough for a zero-parameter listing operation.

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

Deploy Server