Skip to main content
Glama
Sign In
Kdenlive MCP Server

Kdenlive MCP Server

by Va1bhav512
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

timeline_remove_clip

Remove a specific clip from a timeline track by specifying the track ID and the clip's index.

Instructions

Delete a clip from the timeline.

Args: track_id: Track containing the clip. clip_index: 0-based index of the clip within the track.

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": {
      "track_id": "<track_id>",
      "clip_index": "<clip_index>"
    },
    "name": "timeline_remove_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYes
clip_indexYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only says 'Delete' and lists arguments. It does not disclose reversibility, shift of remaining clip indices, invalid-index behavior, or any side effects.

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 one action sentence plus two concise parameter lines, with no filler. The key action is front-loaded and every line earns its place.

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

Completeness4/5

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

The tool is simple, with two flat integer parameters and an output schema, and both parameters are fully explained. It is complete enough for correct invocation, though it would benefit from a note on destructive behavior or index-shift effects.

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

Parameters5/5

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

Schema coverage is 0%, so the Args section must supply all parameter meaning, and it does for both parameters. track_id is identified as the containing track, and clip_index is explicitly described as the 0-based index within that track.

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 states a specific action and resource: 'Delete a clip from the timeline.' This clearly distinguishes it from sibling tools like timeline_remove_track and bin_remove_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?

No explicit when-to-use or alternative guidance is provided; the intended use is implied by the verb and resource. An agent can infer this is the tool for removing timeline clips, but the description does not contrast it with similar clip/track operations.

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