resolve-ai-bridge

Overview Schema Source Related Servers Discussions Admin

change_clip_speed

Alter a clip's constant speed in DaVinci Resolve while preserving Fusion connections, timeline duration, and linked audio. Supports multipliers or percentages, with optional frame interpolation.

Instructions

Change constant video speed through a bridge-owned Fusion TimeSpeed node.

Existing Fusion connections are preserved. Timeline duration and linked audio are unchanged. Speed 1 neutralizes only bridge-owned nodes. Reverse is not currently verified. Clip-attributes mode changes EVERY use of the source media, relative to its current FPS.

Args: item_id: Target clip id (e.g. 'V1.1', 'playhead', or clip name). Defaults to active clip under playhead. speed: Speed multiplier (e.g. 0.75 for 75% speed / 25% slower, 0.5 for half-speed, 2.0 for 2x speed, 1.0 for normal). speed_percent: Speed as a percentage (e.g. 75.0 for 75% speed). slow_down_percent: Slowdown percentage (e.g. 25.0 to slow down by 25% -> 0.75x speed). speed_up_percent: Speedup percentage (e.g. 50.0 to speed up by 50% -> 1.5x speed). interpolate_frames: Whether to enable smooth frame interpolation/blending (default True). reverse: Must be False; use Resolve manually for reverse playback. method: Implementation method: 'fusion' (native TimeSpeed node, default) or 'clip_attributes' (MediaPoolItem FPS).

Input Schema

TableJSON Schema

Name	Required	Default
`speed`	No
`method`	No	fusion
`item_id`	No	playhead
`reverse`	No
`speed_percent`	No
`speed_up_percent`	No
`slow_down_percent`	No
`interpolate_frames`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses that existing Fusion connections are preserved, timeline duration and linked audio remain unchanged, speed 1.0 neutralizes only bridge-owned nodes, reverse is not verified, and clip_attributes mode affects every use of the source media. This gives an agent an unusually complete picture of side effects and limitations.

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

Conciseness5/5

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

The description is longer than average, but every sentence earns its place given eight parameters and two behavioral modes. It front-loads the core purpose, then states side effects, mode-specific behavior, and parameter semantics in a logical order. The examples are repetitive only in the sense that they deliberately disambiguate the four speed-specification parameters.

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?

The description covers behavior, side effects, method selection, defaults, and limitations, which is strong for a tool with no annotations. The main gap is that it does not state what happens if multiple speed parameters (speed, speed_percent, slow_down_percent, speed_up_percent) are supplied simultaneously, which is a plausible ambiguity an agent could hit when constructing arguments.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameter descriptions, but the Args block fully compensates by explaining each parameter with concrete examples and conversions, e.g. 'slow_down_percent: 25.0 to slow down by 25% -> 0.75x speed.' It also clarifies defaults like item_id defaulting to 'playhead' and interpolate_frames defaulting to True, adding meaning far beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Change constant video speed through a bridge-owned Fusion TimeSpeed node.' It further clarifies the two implementation modes (fusion vs. clip_attributes), which distinguishes this tool's behavior from other editing tools and prevents conflation with generic clip-property setters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear contextual guidance, such as 'Clip-attributes mode changes EVERY use of the source media' and 'Reverse must be False; use Resolve manually for reverse playback.' It does not explicitly compare against sibling tools like set_clip_property, but it does explain when each internal method is appropriate and states a firm exclusion for reverse playback.

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