Skip to main content
Glama

clip_update

Modify media pool clips in DaVinci Resolve: rename, set clip color, flags, metadata, properties, and source in/out marks, or clear flags, color, and marks.

Instructions

Modify media pool clips: rename (single item), clip color, flags, metadata ({"Scene":"12","Take":"3", "Description":..., "Keywords":...}), clip attributes/properties ({"Input Color Space":"Rec.709", "Super Scale":2, "Clip Name":...}), source in/out marks (seconds of source). clear_flags: a color or 'All'.

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": {
      "items": "<items>"
    },
    "name": "clip_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNo
itemsYes
mark_inNo
mark_outNo
metadataNo
add_flagsNo
propertiesNo
clear_colorNo
clear_flagsNo
clear_marksNo
third_party_metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations are absent, so the description carries the full burden. It does disclose useful behavior beyond the schema: example metadata/property shapes, that marks are in seconds of source, that clear_flags accepts a color name or 'All', and that rename is single-item only. It omits what happens when conflicting options are supplied (e.g. color vs clear_color), whether changes are reversible, and any permission or error behavior for a destructive mutation.

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 front-loaded sentence plus a short trailing note on clear_flags; every clause maps to a capability and the parenthetical examples are dense but useful. The telegraphic style ("flags", "clip color") risks ambiguity but wastes no words.

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 12-parameter mutation tool with no annotations and no output schema, this covers most modifiable facets but leaves the required 'items' argument and third_party_metadata unexplained, and says nothing about return values or atomicity. Adequate to attempt a call, not sufficient to call it confidently.

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 must compensate, and it partially does by giving example payload shapes for metadata and properties and units for mark_in/mark_out. Key gaps remain: the required 'items' parameter (presumably clip identifiers, single vs list) and 'third_party_metadata' are never described, and clear_color is only obliquely implied by "clip color".

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?

States a specific verb ("Modify") and resource ("media pool clips") and then enumerates the concrete facets it can change: name, color, flags, metadata, properties, in/out marks. An agent can distinguish this from narrow siblings like clip_label or clip_properties, though the description never explicitly contrasts with them.

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?

Implicit guidance exists: "rename (single item)" warns that naming only works for one clip at a time, and "seconds of source" clarifies mark units. However, there is no explicit when-to-use/when-not, no mention of the sibling tools that handle narrower operations, and no prerequisites or failure conditions.

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