Skip to main content
Glama

clip_label

Rename timeline clips and manage their labels by setting or clearing colors, adding or clearing flags, and enabling or disabling clips in DaVinci Resolve.

Instructions

Rename timeline clips, set/clear clip color, add/clear flags, enable/disable clips.

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": {
      "clips": "<clips>"
    },
    "name": "clip_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
clipsYes
colorNo
enabledNo
add_flagsNo
clear_colorNo
clear_flagsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral burden. It reveals that multiple mutation types (rename, color, flags, enabled) are bundled, but says nothing about permissions, reversibility, what null means for each field, or whether omitted fields are left untouched — all critical for a mutation tool.

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

Conciseness4/5

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

One dense, front-loaded sentence with parallel verb phrases and no filler. It is slightly list-like, but every clause names a supported operation.

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 7-parameter mutation tool with no annotations and no output schema, the description is thin: it never explains the required clips argument, how fields combine in a single call, or what the caller gets back. It orients but does not enable a correct 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?

Schema description coverage is 0% across 7 parameters, and the description does map meaning onto most of them (name, color, clear_color, add_flags, clear_flags, enabled). However the single required parameter, clips, is never characterized — no hint whether it takes IDs, indices, or clip objects — and the type mismatch between add_flags (array) and clear_flags (string) goes unexplained.

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?

Uses specific verbs tied to a concrete resource: rename clips, set/clear color, add/clear flags, enable/disable. An agent immediately knows the family of operations, though it is not distinguished from plausible siblings like clip_update or clip_properties.

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 statement of when to use this over alternatives, no prerequisites, no exclusions. The reader must infer that this is the label/metadata mutator versus clip_update or clip_properties purely from the verb list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.