Skip to main content
Glama

create_multicam_clip

Create multicam clips from selected source clips in DaVinci Resolve, with options for angle sync, frame rate, audio mode, and gap splitting.

Instructions

Create multicam clip(s). options (see get_api_type('MulticamOptions')): name, startTimecode, frameRate, angleSyncMode (MULTICAM_ANGLE_SYNC_*), angleNameMode (MULTICAM_ANGLE_NAME_*), multicamAudioMode (MULTICAM_AUDIO_*), detectSameCameraClipsMode (MULTICAM_DETECT_*), splitAtGaps, useFullClipExtents, createBinForSourceClips. Constant names are converted automatically.

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": {
      "clips": "<clips>"
    },
    "name": "create_multicam_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
optionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds useful behavior context by enumerating what the options object controls and noting that constant names are converted automatically, but it never explains what the required clips strings represent or what the call returns.

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?

Two sentences, front-loaded with the action, followed by a compact enumerated list of option fields. Every clause carries information and nothing is redundant.

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?

With no output schema and only two parameters, the description covers the options surface well enough that an agent could populate it; the missing piece is the meaning and format of the required clips array. Given the annotation coverage and the explicit get_api_type pointer for full option details, this is close to complete.

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 coverage is 0%, so the description must compensate, and it partially does: it names nine meaningful option fields and their MULTICAM_* constant prefixes, which is substantial value over a free-form object with additionalProperties=true. However, the single required parameter 'clips' (an array of strings) is left entirely unexplained, which is a real gap for a create operation.

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 opens with a specific verb plus resource, 'Create multicam clip(s)', which tells an agent exactly what the tool produces. It does not differentiate from other creator siblings such as create_compound_clip or create_stereo_clip, so the agent must infer that multicam is a distinct clip type rather than being told.

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 or when-not-to-use guidance, no prerequisite (e.g. source clips must already be in the project), and no comparison against the other clip-creation tools. The only routing hint is a pointer to get_api_type('MulticamOptions') for the options shape, which is a lookup aid rather than usage guidance.

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