Skip to main content
Glama

multicam_create

Create a multicam clip from selected media pool clips by syncing angles using timecode, audio, marker, in, or out points, with options for audio mode and angle naming.

Instructions

Create a multicam clip from media pool clips. sync: in | out | timecode | audio | marker. audio_mode: adaptive | source | reference | all. angle_names: sequential | angle | camera | clip | file.

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": {
      "items": "<items>"
    },
    "name": "multicam_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
syncNotimecode
itemsYes
audio_modeNosource
angle_namesNosequential
start_timecodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and does not meet it. It does not say whether a new clip/bin is created and where it lands, whether source media is copied or referenced, what happens on invalid item names, or whether the operation is reversible; only the word "Create" signals mutation.

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?

Tight and front-loaded: purpose first, then compact value lists with no filler sentences. The lists are terse to the point of being cryptic, but no sentence is wasted.

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?

A mutation tool with 6 parameters, zero schema coverage, no annotations, and no output schema requires substantially more description than this. The most important gaps are the required 'items' parameter and the effect of each sync/audio mode, neither of which is addressed.

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 6 parameters, so the description must compensate and only partly does. It enumerates allowed values for sync, audio_mode, and angle_names but never explains what those modes mean or what the sync targets, and it says nothing about the required 'items' array, 'name', or 'start_timecode'.

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?

States a specific verb and resource: "Create a multicam clip from media pool clips." That is clearly distinguishable from project_create/timeline_create/compound_create by naming the resource (multicam clip) and the input source (media pool clips), though it does not explicitly point at any sibling for the adjacent operations.

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 / when-not-to-use guidance, no prerequisites, and no mention of how this differs from compound_create or timeline_create. The description jumps straight from the purpose sentence into bare enum value lists, leaving the agent to infer selection criteria on its own.

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