Skip to main content
Glama

set_keyframe_mode

Set the Color page keyframe mode to all, color, or sizing to control which parameters receive keyframes in DaVinci Resolve.

Instructions

Set the Color page keyframe mode.

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": {
      "mode": "<mode>"
    },
    "name": "set_keyframe_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

Annotations establish that this is a non-read-only, non-destructive, closed-world mutation, but the description adds nothing beyond that: it doesn't say whether the mode is persisted, whether it applies retroactively to existing keyframes, or what changes visually. For a mutation with zero annotation detail about effects, the description carries a burden it doesn't meet.

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 short sentence with no filler, and the action is front-loaded. Its brevity is efficient, though it edges toward under-specification rather than crispness.

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 mutation tool with no output schema and 0% parameter description coverage, the definition should explain what the mode controls and what each enum value means. As written, an agent knows only the name of the setting, not its consequences.

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

Parameters4/5

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

Schema description coverage is 0% for the single parameter, but the enum values (all, color, sizing) are largely self-describing in context and the required flag is in the schema. The description adds nothing beyond the schema, so this sits at the neutral baseline.

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 specific verb ("Set") and a specific resource ("the Color page keyframe mode"), which is distinguishable from sibling setters like set_project_settings or set_timeline_settings. It stops short of explaining what a keyframe mode governs, but the purpose is identifiable.

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 prerequisites (e.g., must the Color page be active or a clip selected?), and no mention of what this affects versus other settings tools. The agent must infer all context.

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