Skip to main content
Glama

update_clip

Modify a DaVinci Resolve media pool clip by renaming it, changing its color, editing properties and metadata, managing flags, and updating audio mapping.

Instructions

Change a media pool clip: rename, clip color ("" clears), clip properties (e.g. "Clip Name", "Input Color Space", "Data Level", "Reel Name"...), metadata (e.g. Scene, Take, Comments), third-party metadata, flags and audio mapping (JSON string, see get_api_docs('Audio Mapping')).

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": {
      "clip": "<clip>"
    },
    "name": "update_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
nameNo
colorNo
metadataNo
add_flagsNo
propertiesNo
clear_flagsNo
audio_mappingNo
third_party_metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes real behavior of its own — the "" convention that clears a clip color, and the separate add_flags/clear_flags axes for the same flag set — but never says whether omitted fields are left untouched or whether audio_mapping replaces the entire mapping. For a 9-parameter mutation that merge-versus-replace question is the main behavioral gap.

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?

A single sentence that front-loads the verb and resource, then enumerates facets compactly with parenthetical examples rather than prose. Dense but appropriate for nine parameters, with no filler sentences.

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?

With nine parameters, no schema descriptions, no output schema and no destructive/write detail, the description does a fair job of naming what can be changed but leaves the required clip argument, accepted object shapes, and replacement semantics undocumented. An agent would likely need get_api_docs before calling it safely.

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%, so the description has to carry all 9 parameters, and it covers most of them: name, color clearing semantics, example property keys (Clip Name, Input Color Space, Data Level, Reel Name), example metadata keys (Scene, Take, Comments), third-party metadata, and flags. However it never mentions the required clip parameter, its identifier form, or what object shape metadata/properties accept, leaving meaningful gaps at 0% coverage.

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?

"Change a media pool clip" gives a specific verb plus a precisely scoped resource, and the list of editable facets (rename, color, properties, metadata, flags, audio mapping) makes the tool's surface unambiguous. It separates itself from siblings by resource (a clip, not an item or track), though it never names update_item or update_track as the alternative for those resources.

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?

There is no statement of when to reach for update_clip versus update_item/update_track, and no prerequisites or exclusions. The only routing help is the inline pointer to get_api_docs('Audio Mapping'), which explains a parameter's format rather than when to use this tool.

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