Skip to main content
Glama

transition_add

Adds a transition to clip edges in DaVinci Resolve so you can apply video or audio transitions with type, position, alignment, duration, and category controls.

Instructions

Add a transition to clip edges. position: start | end | both; alignment: center | left | right (left = ends at the cut, right = starts at the cut); duration in seconds. category: simple | fusion | ofx | audio. Common types: 'Cross Dissolve', 'Dip To Color Dissolve', 'Smooth Cut', 'Additive Dissolve', 'Blur Dissolve', 'Push', 'Slide', 'Wipe', 'Iris', 'Zoom' ; audio: 'Cross Fade +3 dB', 'Cross Fade 0 dB', 'Cross Fade -3 dB'. The neighbouring clip needs enough handle media for centered transitions.

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": "transition_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoCross Dissolve
clipsYes
categoryNosimple
durationNo
positionNoend
alignmentNocenter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add a genuine behavioral caveat - 'The neighbouring clip needs enough handle media for centered transitions' - which is real operational knowledge not present in the schema. But it says nothing about what happens if a transition already exists at that edge, whether the operation is reversible, or what failures look like, which matters for an unannotated 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?

The parameter semantics are front-loaded and the enum lists are compact. The type catalogue is long but informative rather than redundant. Slight density cost from packing four parameter glosses into one sentence, but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, unannotated, no-output-schema mutation tool the description covers most of what an agent needs: value domains, units, and a media-precondition. It leaves the required `clips` input format and the return/failure behavior unexplained, which keeps it short of complete.

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

Parameters4/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 largely does: it defines position (start/end/both), alignment (center/left/right, with the left/right semantics spelled out as 'ends at the cut' / 'starts at the cut'), duration units in seconds, category values, and enumerates common transition type names including audio variants. The one gap is the required `clips` parameter, whose accepted identifier format is never described.

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 opens with a specific verb and resource: 'Add a transition to clip edges.' An agent immediately understands the operation. It does not, however, differentiate itself from adjacent siblings such as clip_fade or the other *_add tools, so it stops short of a 5.

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?

Usage context is implied rather than stated - the agent can infer it applies when a transition is wanted at a clip boundary, and the closing note about handle media hints at a precondition. There is no explicit when-to-use vs. when-not, and no routing to alternatives like clip_fade.

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