Kdenlive MCP Server

by Va1bhav512

Overview Schema Source Related Servers Discussions Admin

Python

Local

clip_add_note

Add or update a note on a bin clip to document or organize it in Kdenlive. Provide the clip ID and note text.

Instructions

Add / update note for bin clip.

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>",
      "note": "<note>"
    },
    "name": "clip_add_note"
  }
}

Input Schema

Name	Required	Description	Default
`note`	Yes
`clip_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The 'Add / update' phrasing does signal an upsert-like mutation, but it does not say whether an existing note is overwritten, whether an empty string clears the note, or what happens when clip_id is invalid.

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 focused sentence with the core operation front-loaded and no filler. Every word contributes to meaning, making it appropriately sized for the tool's simplicity.

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?

The tool is low complexity with two simple string parameters and an output schema, so a detailed return-format explanation is unnecessary. However, because there are no annotations and no usage or note-clearing semantics, the description is only minimally complete for safe invocation.

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

Parameters2/5

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

Schema description coverage is 0%, and the description adds almost no parameter-level meaning beyond the self-explanatory names 'clip_id' and 'note'. It hints that clip_id refers to a bin clip, but it does not clarify note format, length, clearing behavior, or where to obtain a valid clip_id.

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 states a clear action ('Add / update') and a distinct resource ('note for bin clip'), so an agent can tell this apart from the many timeline and clip tools in the sibling list. It does not explicitly contrast with a sibling, but the unique 'note' target and 'bin clip' scope make the purpose unambiguous.

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?

There is no guidance on when to use this tool, whether the clip must already exist in the bin, or how it relates to other clip operations. The sibling list shows many clip-related alternatives, but the description never explains why an agent should choose this one over another.

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

Deploy Server