resolve-ai-bridge

Overview Schema Source Related Servers Discussions Admin

animate_zoom

Add keyframed zoom and framing changes to DaVinci Resolve clips, using easing curves, multi-keyframe paths, or AI presets for punch-ins, reveals, and pull-outs.

Instructions

Animate a clip's scale and framing over time (smooth zooms, punch-ins, rebounds, pull-outs, multi-keyframe paths).

Supports full Zoom In and Zoom Out (direction='out'), all standard easing curves (linear, ease_in, cubic_in, ease_out, cubic_out, ease, cubic_ease, circular_ease, rebound_in, rebound_out, elastic_out), multi-keyframe arrays, and automated AI presets (punch_in, pop_in, slow_push, dramatic, reveal, cinematic). Joins the bridge's Fusion chain: blur, spotlight and your own Fusion nodes stay connected. reset=True removes only the bridge zoom node. Frames: start_frame/end_frame and keyframe 'frame' count from the clip's first frame (0). timeline_start_frame/timeline_end_frame and keyframe 'timeline_frame' take absolute timeline frames.

Input Schema

Name	Required	Default
`reset`	No
`easing`	No	smootherstep
`preset`	No
`item_id`	No	playhead
`end_zoom`	No
`direction`	No	in
`end_frame`	No
`keyframes`	No
`start_zoom`	No
`start_frame`	No
`track_index`	No
`target_center_x`	No
`target_center_y`	No
`timeline_end_frame`	No
`timeline_start_frame`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.13.0Oct 21, 2026

addedInput schema / properties / timeline_end_frame

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Timeline End Frame"
+}

addedInput schema / properties / timeline_start_frame

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Timeline Start Frame"
+}

First observedv0.1.0Sep 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavioral context: it joins the bridge's Fusion chain so blur/spotlight/custom Fusion nodes stay connected, reset=True removes only the bridge zoom node, and reset is scoped. It stops short of stating permission requirements, failure modes, or idempotency.

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?

Front-loaded with the core purpose in the first sentence, then grouped option lists, then frame-coordinate semantics. Dense but every sentence carries information; the parenthetical value lists are long but usable as reference.

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?

An output schema exists so return values need not be explained, and the description covers the genuinely tricky parts of a 15-parameter unannotated mutation tool (Fusion chain interaction, reset scope, frame coordinate systems). Remaining gaps are the unmentioned target_center and track/item selection parameters.

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% across 15 params, so the description must compensate, and it does substantially: it lists the easing values, direction='out', the AI presets, keyframe arrays, and the critical clip-relative vs absolute-timeline frame semantics for start_frame/end_frame, timeline_* variants, and keyframe keys. It leaves target_center_x/y, item_id, track_index, and start_zoom/end_zoom meaning undocumented.

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?

States a specific verb ("Animate") and resource (a clip's scale and framing over time) with concrete sub-modes: smooth zooms, punch-ins, rebounds, pull-outs, multi-keyframe paths. An agent can immediately tell this is the zoom/scale animation tool, distinct from sibling animation tools like animate_color_fx or apply_blur_effect.

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?

The description enumerates the capabilities and option values, which implies when the tool applies, but never states when to use it over alternatives such as set_clip_transform (static transform) or the other Fusion effect appliers. No exclusions or sibling routing are provided, so usage is only implied.

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