davinci-mcp

Overview Schema Source Related Servers Discussions Admin

Gallery (write)

gallery_write

Destructive

Change DaVinci Resolve gallery state—create albums, import/export or grab stills, rename albums, and set labels—with each change read back for verification.

Instructions

Change gallery state; may overwrite current values. Every change is read back from Resolve (receipt.verified=false means it did not take). op.action (params; * = required):

create_album(kind): Create a still album or a PowerGrade album.
export_stills(album, stills, folder*, prefix, format): Export stills to a folder (needs the Gallery panel open in Resolve).
grab_still(scope, frame_source): Grab a still from the current clip, or from all clips, into the current album.
import_stills(album, paths*): Import still files into an album (default: current).
rename_album(album*, new_name*): Rename a still or PowerGrade album.
set_current_album(album*): Make a still album the current one.
set_still_label(album, still*, label*): Set the label of a still. Shortcuts (prefer them for whole tasks):
workflow_write.apply_look: Apply a LUT to every video item, group them in a color group and grab a still. One call instead of grab_still. Calls known in advance (a sequence, the same change on several items): ONE batch_run.

Input Schema

Name	Required	Description
`op`	Yes	{action, ...params}. Parameters per action: see the description or this server's describe_action tool.
`dry_run`	No	true: return the planned effect, change nothing.
`snapshot`	No	true: back up the timeline/project first; omitted: server policy.

Output Schema

Name	Required	Description	Default
`job`	No
`plan`	No
`status`	Yes
`receipt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.4Nov 1, 2026
- addedInput schema / properties / dry_run / description
```
Added value: +"true: return the planned effect, change nothing."
```
- addedInput schema / properties / snapshot / description
```
Added value: +"true: back up the timeline/project first; omitted: server policy."
```
First observedv0.1.0Nov 1, 2026

TDQS

A5/5.0

Behavior5/5

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

Goes well beyond the annotations: warns "may overwrite current values", discloses the read-back verification semantics ("receipt.verified=false means it did not take"), and states the prerequisite that export_stills needs the Gallery panel open in Resolve. These are non-obvious failure modes an agent could not infer from destructiveHint=true alone.

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?

Front-loads the destructive warning before any detail, then presents a scannable bulleted action list, then a clearly labeled shortcuts section. Dense but every line carries either an action contract or a routing rule; nothing is redundant with the schema.

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?

A destructive multi-action tool with a polymorphic `op` parameter is fully covered: mutation risk, verification signal, prerequisites, batching escape hatch, and per-action params are all present, and the output schema plus receipt.verified note covers return semantics.

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?

Although schema coverage is nominally 100%, the `op` schema is an open object that only says "see the description", so the description is the real source of per-action parameter contracts — it names which params each action takes and marks required ones with asterisks. dry_run and snapshot are separately documented in the 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?

Opens with a specific verb+resource ("Change gallery state") and then enumerates the seven concrete actions (create_album, export_stills, grab_still, import_stills, rename_album, set_current_album, set_still_label). It is unambiguously the write counterpart to gallery_read/gallery_delete, so an agent can route without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes away from itself: "Shortcuts (prefer them for whole tasks)" points to workflow_write.apply_look instead of grab_still, and "Calls known in advance... ONE batch_run" names the batching alternative. It also defers to describe_action for per-action parameter detail, giving a complete decision path.

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