Skip to main content
Glama

update_item

Modify a DaVinci Resolve timeline item's name, color, speed, flags, inspector properties, voice isolation, or output blanking settings.

Instructions

Change a timeline item. properties: Inspector values validated all-or-nothing (Pan, Tilt, ZoomX/Y, RotationAngle, Crop*, Opacity, CompositeMode, RetimeProcess, Scaling...; constants by name e.g. "COMPOSITE_SCREEN"; see get_api_type('TimelineItemProperties')). speed: {Percentage, PitchCorrection, StretchKeyframesToFit, RippleTimeline}. voice_isolation: {isEnabled, amount}. output_blanking: {Top, Bottom, Left, Right}.

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": {
      "item": "<item>"
    },
    "name": "update_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
nameNo
colorNo
speedNo
enabledNo
fade_inNo
fade_outNo
add_flagsNo
propertiesNo
clear_flagsNo
burn_in_presetNo
output_blankingNo
voice_isolationNo
color_output_cacheNo
fusion_output_cacheNo
source_audio_channel_mappingNo
use_timeline_output_blankingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, closed-world mutation. The description genuinely adds value with "Inspector values validated all-or-nothing," a real behavioral trait that warns partial property updates will fail entirely. It stops short of saying whether omitted top-level fields (name, color, enabled) are left untouched, which is the key ambiguity for a 17-param patch-style tool.

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

Conciseness3/5

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

It is compact and front-loads the verb, but the bulk is a schema restatement in one run-on block with no grouping or line structure. Priority is inverted: the complex nested objects get the words while the simple scalar params get none.

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 17-parameter mutation with no output schema, the description covers the hardest nested payloads and flags the all-or-nothing validation rule, which an agent must know. It leaves the semantics of the many nullable top-level fields unexplained, so an agent still cannot confidently construct a call from the definition alone.

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 coverage is 0% and the schema types speed, voice_isolation and output_blanking as bare objects with additionalProperties, so the description's enumeration of their sub-keys ({Percentage, PitchCorrection, ...}, {Top, Bottom, Left, Right}) is the only documentation those params have. That is real added meaning, but roughly a dozen parameters (name, color, fade_in/out, add_flags, clear_flags, burn_in_preset, the output-cache flags, source_audio_channel_mapping) remain entirely undocumented, so coverage is partial rather than compensating.

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 timeline item" gives a specific verb plus resource, so the agent knows this is a mutation on a timeline item rather than a clip or track. It does not, however, contrast itself with update_clip or update_track, both of which could plausibly be chosen instead.

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 use this tool versus siblings, no prerequisites, and no note on which fields are safe to change. The only navigational aid is the pointer to get_api_type('TimelineItemProperties') for valid property names, which helps discovery but is not usage guidance.

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