Skip to main content
Glama

manage_color_group

Create, rename, or delete color groups, then assign timeline items to a group or remove them from it in DaVinci Resolve.

Instructions

Create / rename / delete a color group, assign timeline items to it, or remove items from their group.

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_color_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
itemsNo
actionYes
new_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=false and destructiveHint=false, so the description's main job is to explain the mutation surface. It reveals the operation set but says nothing about whether a deleted group's items survive, whether renaming requires the group to exist, whether either mutation is reversible, or what errors look like. There is also visible tension between the explicit 'delete a color group' / 'remove items' wording and destructiveHint=false; this is arguably defensible if deletion only drops grouping metadata while clips remain, but the description never resolves it.

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?

A single front-loaded sentence that enumerates the action space in the same order and vocabulary as the enum, with zero filler. Nothing could be cut without losing an operation.

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?

For a 4-parameter, single-required-field mutation tool with no output schema, the description covers the full action space adequately. Its remaining gap is the per-action parameter contract, which is the one thing an agent needs and the schema (0% coverage) cannot supply.

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 must carry parameter meaning. It does partially: 'rename' hints at new_name, 'assign timeline items' hints at items, and the group is impliedly identified by name. However, the name-vs-new_name split is never explained, nor is it stated which parameters are required for which action (e.g., is 'items' needed for remove, is 'name' the group identifier for assign).

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?

The description names a concrete resource (color group) and enumerates the exact operations: create, rename, delete, assign items, remove items. That is far more specific than the bare name 'manage_color_group' and maps one-to-one onto the action enum. It does not explicitly contrast itself with the read-side sibling list_color_groups, so it stops just short of a 5.

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 verb list implies when the tool is applicable (any mutation of color groups), but there is no explicit guidance such as 'use list_color_groups first to find the group name' or 'call this after the group exists'. There are no stated preconditions, no alternatives named, and no exclusions, so the agent must infer routing.

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