resolve-ai-bridge

Overview Schema Source Related Servers Discussions Admin

apply_blur_effect

Apply static or animated Gaussian, defocus, or directional blur to a full frame or masked region in DaVinci Resolve, with keyframes and reset support.

Instructions

Apply a static or gradual blur to the full frame or a masked region (gaussian, defocus, directional).

Each mask_name is its own blur; reusing a name updates it. Keyframes may set frame, blur_size, center_x, center_y, width, height and easing. Joins the bridge's Fusion chain without cutting out your own nodes. reset=True removes every bridge blur and leaves other nodes connected. 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
`width`	No
`easing`	No	smootherstep
`height`	No
`animate`	No
`item_id`	No	playhead
`center_x`	No
`center_y`	No
`end_blur`	No
`blur_size`	No
`blur_type`	No	gaussian
`end_frame`	No
`keyframes`	No
`mask_name`	No	1
`soft_edge`	No
`mask_shape`	No	rectangle
`start_blur`	No
`start_frame`	No
`track_index`	No
`corner_radius`	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 / keyframes

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Keyframes"
+}

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.9/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 reusing a mask_name updates an existing blur, that keyframes drive parameters, that reset=True removes every bridge blur while leaving other nodes connected, and that it joins the Fusion chain without cutting out existing nodes. It omits permission/reversibility context, but the mutation semantics are unusually well covered.

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 purpose, then layers mechanics and frame-counting rules in compact sentences with no filler. Structurally sound, though a few sentences are dense enough to require re-reading.

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 most consequential behaviors for a 22-parameter tool (mask reuse, keyframe support, reset scope, frame indexing). It falls short only on finer per-parameter semantics.

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 22 parameters, so the description must compensate. It clarifies mask_name semantics, the keyframe fields, reset, and the distinction between clip-relative frames and absolute timeline frames, but a large share of parameters (soft_edge, mask_shape, corner_radius, item_id, track_index, start_blur/end_blur, animate, easing) remain 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 (apply) plus resource (blur effect) and enumerates the supported variants (gaussian, defocus, directional) and scope (full frame or masked region). This clearly distinguishes it from siblings like apply_spotlight_mask or animate_zoom without the agent needing to open schemas.

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 explains how to operate the tool (mask_name reuse, keyframes, reset) but never states when to choose it over alternatives such as apply_spotlight_mask or animate_color_fx, nor any prerequisites. Usage is implied through mechanics rather than explicitly routed.

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