Skip to main content
Glama
Sign In
Kdenlive MCP Server

Kdenlive MCP Server

by Va1bhav512
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

timeline_set_zoom

Set the Kdenlive timeline zoom level from 0.1 to 10.0 to adjust the view for detailed editing or an overview of the project.

Instructions

Set timeline zoom level (0.1 .. 10.0).

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": {
      "zoom": "<zoom>"
    },
    "name": "timeline_set_zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoomYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does convey that this is a mutating operation ('Set') and constrains the value range, but it does not mention failure behavior, whether the zoom applies to the active timeline, or any side effects. For a simple one-value setter, this is minimally adequate.

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 with no filler. The core action is front-loaded and the range is appended compactly. Every word 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?

Given the tool's low complexity, single required parameter, and presence of an output schema, the description is largely complete. It clearly states what the tool does and what value range is accepted. A small gap is the lack of detail about clamping or error handling for out-of-range values, but this is not blocking for correct invocation.

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 input schema provides only the parameter name and type, with no description or min/max. The tool description adds the critical semantic constraint '(0.1 .. 10.0)', which directly documents the valid range for the 'zoom' parameter. This compensates well for the otherwise sparse schema.

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 uses a specific verb ('Set') and resource ('timeline zoom level'), and the numeric range adds precision. It clearly differentiates from the sibling timeline_get_zoom, which is the getter counterpart.

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 description clearly indicates that this tool is for changing the zoom level, not reading it, so the intended context is clear. It does not explicitly name alternatives or exclusion cases, but the setter/getter distinction with timeline_get_zoom makes the usage obvious.

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