Skip to main content
Glama
Sign In
Kdenlive MCP Server

Kdenlive MCP Server

by Va1bhav512
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

guide_update

Update an existing guide's label, comment, position, or type in a Kdenlive project by specifying its ID.

Instructions

Update guide properties.

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": {
      "guide_id": "<guide_id>"
    },
    "name": "guide_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
commentNo
guide_idYes
positionNo
guide_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.4/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 burden of behavioral disclosure, but 'Update guide properties' only signals mutation. It doesn't say whether omitted properties are preserved, whether null values clear fields, whether it is reversible, or what side effects occur on the guide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and has no filler, but it is under-specified rather than concisely informative. It is a single vague phrase that omits essential details, so brevity does not compensate for its lack of substance.

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?

For a tool with five parameters, one required and no annotations, this description is far too thin. It doesn't state prerequisites, the exact set of updatable properties, or behavior on success/failure, even though an output schema is present.

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

Parameters1/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 no parameter information at all. It doesn't identify guide_id as the required identifier, nor explain that label, comment, position, and guide_type are optional/nullable or what their update semantics are.

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 and resource: 'Update guide properties', which distinguishes it from siblings such as guide_add, guide_remove, guide_get, and guide_list. However, it doesn't enumerate which guide properties are modifiable or mention that an existing guide_id is required, so it stops short of a fully precise purpose.

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 about when to use this tool instead of its alternatives. The only signal is the verb 'Update', which implies an existing guide, but the description never states that or warns against using it for creation/deletion.

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