resolve-ai-bridge

Overview Schema Source Related Servers Discussions Admin

animate_color_fx

Animate rainbow hue rotation and subtle luminance flicker on a Resolve clip using a bridge-owned Fusion ColorCorrector, with options to reset the node or report unsupported parts.

Instructions

Animate rainbow hue rotation and a subtle luminance flicker with a bridge-owned Fusion ColorCorrector.

Reports any part this build's ColorCorrector cannot do. 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	Description	Default
`reset`	No
`flicker`	No
`item_id`	Yes
`rainbow`	No
`end_frame`	No
`saturation`	No
`start_frame`	No
`tint_strength`	No
`rainbow_cycles`	No
`flicker_amplitude`	No
`flicker_frequency`	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.

Changed3 schema fields changedv1.13.0Oct 21, 2026

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

A4.5/5.0

Behavior5/5

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

Since no annotations were provided, the description carries the full burden, which it meets exceptionally well. It details critical behaviors such as reporting limitations ('Reports any part this build's ColorCorrector cannot do') and the destructive nature of a specific parameter ('reset=True removes the bridge node').

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 description efficiently front-loads the core function and then systematically details the technical nuances (frame modes, reset behavior). It is dense due to technical complexity but avoids unnecessary fluff.

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

Completeness5/5

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

The definition is highly complete, especially considering the lack of annotations. It covers the functionality, operational limits, critical behavioral side effects (reset), and the precise methodology for time-based parameters.

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?

Given the schema coverage is 0%, the description provides vital semantic context that the schema misses. It precisely defines the two types of frame counting systems (relative: 'frame' count from clip's first frame; absolute: 'timeline_frame'), which is essential for correct usage of multiple timing parameters.

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 clearly states the function: 'Animate rainbow hue rotation and a subtle luminance flicker.' This pinpoints the specific, high-level action of the tool and distinguishes it from other effect or animation tools available.

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 purpose is clear, but the usage guidelines are implicit rather than explicit. It tells the agent what it *does*, but not explicitly when to use it versus other color grading tools or alternatives.

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