Skip to main content
Glama
Sign In
Kdenlive MCP Server

Kdenlive MCP Server

by Va1bhav512
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

guide_list

Retrieve all guide markers on the timeline to review key frames and navigation points in your Kdenlive project.

Instructions

Return all guide markers on the timeline.

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": "guide_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden of conveying safety and side effects. 'Return' does indicate a read-only operation, but the description does not disclose ordering, empty-result behavior, or whether unsaved timeline changes are reflected. It is adequate but minimal.

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 short sentence containing only essential information. It is front-loaded with the action and resource, with no filler or repetition.

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?

Given the tool's very low complexity, no parameters, and an existing output schema, the description covers everything needed to invoke it correctly. The phrase 'all guide markers' clarifies scope, and the output schema handles return-value details.

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 and the input schema is empty, so there is no parameter detail to add. The description correctly aligns with the schema's implicit meaning by indicating a single, unfiltered listing operation.

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 verb ('Return') and a clear resource with scope ('all guide markers on the timeline'). It is immediately distinguishable from the sibling guide_get tool, which implies fetching a specific guide rather than listing all.

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 versus alternatives such as guide_get, guide_list, or marker_list. An agent must infer the appropriate choice from the tool name and sibling list rather than from explicit direction.

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