resolve-ai-bridge

Overview Schema Source Related Servers Discussions Admin

keyframe_clip_saturation

Animate a clip's saturation over time from full color to black and white using a bridge-owned Fusion node in DaVinci Resolve, without altering your existing color correction nodes; reset removes it.

Instructions

Animate saturation (e.g. 1.0 full color to 0.0 black and white) with a bridge-owned Fusion node.

Your own ColorCorrector/BrightnessContrast nodes are never changed. reset=True removes the bridge 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	linear
`item_id`	Yes
`end_frame`	No
`start_frame`	No
`end_saturation`	No
`start_saturation`	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.

Changed4 schema fields changedv1.13.0Oct 21, 2026

addedInput schema / properties / easing

Added value: +{
+  "default": "linear",
+  "title": "Easing",
+  "type": "string"
+}

addedInput schema / properties / reset

Added value: +{
+  "default": false,
+  "title": "Reset",
+  "type": "boolean"
+}

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

A3.5/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 well: it discloses that the effect is implemented as a bridge-owned Fusion node, that the user's own ColorCorrector/BrightnessContrast nodes are never touched, and that reset=True removes the bridge node (implying reversibility). It omits permissions/auth and rate limits, but the key side-effect profile is clearly stated.

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-loads the core action before the implementation detail and frame caveats, with no filler sentences. The dense two-line frame-semantics block is justified by the genuine ambiguity between clip-relative and timeline-absolute params.

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 9-param, annotation-free mutation tool with an output schema (so return values needn't be described), the description covers the high-risk areas: what gets modified, what is preserved, and how frames are counted. The main gap is the undocumented 'easing' parameter.

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% across 9 params, so the description must compensate. It handles the hardest ambiguity well, distinguishing clip-relative frame params (start_frame/end_frame, keyframe 'frame') from absolute timeline params (timeline_*), and the 1.0→0.0 example implicitly documents start_saturation/end_saturation. But 'easing' is entirely undocumented and the saturation range/units are only inferred from the example.

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 ("Animate") and resource ("saturation") with a concrete mapping example (1.0 full color to 0.0 black and white). It does not, however, distinguish itself from the sibling animate_color_fx, so an agent can't tell which color-animation tool applies without opening schemas.

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?

The description never says when to prefer this over animate_color_fx or apply_blur_effect, nor does it state any exclusions or prerequisites. The only usage-like content is the reset and frame semantics, which are behavioral rather than selection guidance.

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