Skip to main content
Glama

manage_stills

Grab, import, export, list, delete, or label gallery stills in DaVinci Resolve, including current frames and all clips by source, selected by 1-based indices.

Instructions

Gallery stills: grab the current frame (or all clips: source 1 = first frame, 2 = middle frame) into the current album, list, import image files, export (with .drx grades) to a folder, delete, or set the label of stills selected by 1-based indices (default all).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_stills"
  }
}

Input Schema

NameRequiredDescriptionDefault
albumNoalbum:current
labelNo
pathsNo
actionYes
folderNo
formatNodpx
prefixNostill
sourceNo
indicesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is largely covered. The description adds useful context (grabs land in the current album, export carries .drx grades), but it introduces a "delete" action without saying what is removed or whether it is reversible, which sits uneasily beside destructiveHint=false, and it never mentions that import/export touch the filesystem.

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?

A single dense sentence, but it is front-loaded with the resource and then walks the actions in enum order, so it scans well. Every clause carries information; there is no filler or repetition.

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

Completeness2/5

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

For a 7-action tool with 9 parameters, no output schema, and zero schema descriptions, the definition should state which parameters each action requires (paths for import, folder for export, label for label). It does not, so an agent must guess at per-action parameter coupling.

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%, so the description carries the burden and does add real meaning: source 1 = first frame and 2 = middle frame, indices are 1-based and default to all, and album defaults to the current one. However, folder, paths, prefix, format, and label are never explained, so roughly half the 9 parameters remain opaque.

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?

"Gallery stills" names a concrete resource, and the sentence enumerates the concrete operations (grab, list, import, export, delete, label). An agent can tell this deals with album stills rather than albums, mattes, or presets. It stops short of naming a sibling to distinguish itself from, but the resource scope is specific.

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 lists the available actions but never says when to choose this tool over manage_album or manage_mattes, nor when one action is preferable to another. Usage is implied by the action enumeration rather than stated, leaving the agent to infer intent from the enum alone.

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

Deploy Server

Other Tools