Skip to main content
Glama

color_groups

Manage DaVinci Resolve color groups by creating, listing, renaming, or deleting them, and assigning or removing clips to keep projects organized.

Instructions

Color groups. action: list | create | delete | rename | assign (clips → group name) | remove (clips from group) | clips (list clips of group).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "color_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
clipsNo
actionNolist
new_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it does not say that delete/remove are destructive, whether deleting a group deletes the clips inside it, whether operations are undoable, or what permissions are needed. The only behavioral hint is the terse parenthetical '(clips → group `name`)', which is scope notation rather than disclosed behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loaded with the resource, but the pipe-and-arrow shorthand reads like a schema fragment and takes real effort to parse; a labelled action-to-parameter mapping would have been as short and far clearer.

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?

This is a seven-mode tool with four untyped-by-description parameters, no annotations and no output schema, and the description supplies only a verb menu. Key facts an agent needs — default action behavior, per-action parameter applicability, and whether any mode is destructive — are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description must compensate. It names the valid action values, which is genuinely useful, but never maps name, new_name, or clips to specific actions, nor explains the expected shape of 'clips' (IDs, indices, a list?) — the '→' notation is ambiguous about ordering and format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name plus 'Color groups' identifies the resource, and the action list (list | create | delete | rename | assign | remove | clips) makes the operation set concrete. However, it never explains what a color group is in this domain (a grouping of clips for grading) and does not distinguish it from the sibling color_versions, so an agent gets the verbs but not the domain meaning.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no mention that 'action' defaults to 'list'. The pipe-separated action list is a menu, not guidance; the agent must infer prerequisites such as needing an existing group before assigning or renaming.

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