Skip to main content
Glama
Sign In
Kdenlive MCP Server

Kdenlive MCP Server

by Va1bhav512
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

track_set_hidden

Toggle video track visibility by providing a track ID and a hidden boolean. Control which tracks appear during editing or export.

Instructions

Hide/show a track (video visibility).

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>",
      "hidden": "<hidden>"
    },
    "name": "track_set_hidden"
  }
}

Input Schema

NameRequiredDescriptionDefault
hiddenYes
track_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/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. It states the basic action, but does not mention effects on rendering/export, idempotency, reversibility, or any side effects. For a state-changing tool this is thin.

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 concise sentence that leads with the action and resource, then adds a clarifying parenthetical. There is no wasted wording.

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?

For a low-complexity boolean toggle with only two required parameters, the description is nearly adequate. It lacks explicit usage alternatives and behavioral details, but the output schema and straightforward parameter names reduce the risk of mis-invocation.

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

Parameters3/5

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

The two parameters are simple and their names/types make the meaning almost self-evident. The description adds some value by tying 'hidden' to video visibility, but with 0% schema coverage it does not fully compensate by describing the role of track_id or the exact boolean semantics beyond what the tool name implies.

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 uses a specific verb ('Hide/show') and resource ('a track'), and the parenthetical clarifies that this concerns video visibility. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools such as track_set_muted or track_set_locked.

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?

The phrase 'video visibility' implies this is the tool for controlling visual track visibility, which loosely contrasts with audio-related tools like track_set_muted. However, there is no explicit when-to-use guidance, alternative recommendation, or exclusionary statement.

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