Skip to main content
Glama

manage_multicam

Edits multicam podcast episodes: map camera and mic files to people, sync audio, auto-cut speakers, then render MP4 or export Premiere/FCPXML timelines.

Instructions

Edit a full multicam podcast episode: map every camera and mic file to a person, sync them by audio (with clock-drift correction), auto-cut cameras to whoever is speaking, then render an MP4 or export a Premiere XML / FCPXML timeline that points at the original files. Flow: 'new' (folder or files, people) → check the guessed mapping with 'show' and fix it with 'map' → 'sync' → 'plan' → 'render' or 'export'. 'new' returns the session with guessed roles; calling it again on the same files reopens that edit. 'sync', 'plan' and 'render' start a background job and return job_id: poll job_status, then call 'show'. Mapping fields (people, sources, range_start, range_end, cut_settings, speaker_map, look, removals) apply on 'map', 'sync' and 'plan'; 'render' takes only look and stems. Changing who is in a file or where it sits clears the cut, so run 'plan' again. 'render' skips work when nothing changed and reuses shots it already encoded. Every render checks the finished file (frame count, a full decode, loudness and true peak) and reports outputs.validation; only a broken decode or a picture more than a frame off the cut fails it, the rest are warnings. Other actions: 'list', 'cut' (index, source_id: swap one shot's camera), 'set_cuts' (cuts: replace the whole cut with back-to-back shots), 'activity' (who speaks when, as spans per person), 'previews' (still frames per camera, looks: true adds every color look on every camera), 'preview' (background job: playback proxies, a mic mix and stills, for a browser editor such as podcli cloud), 'delete'. 'cloud' (background job, needs podcli login and Pro: sends previews and the edit to the podcli cloud editor; camera files stay here) and 'pull' (background job: renders the cut made in that editor from the files here). 'export' with review: true writes a review timeline: the whole episode, every camera on its own track under the cut, and each removal left in place, named 'Remove', labelled orange in Premiere and marked with its reason. 'import_timeline' (path) reads an FCP 7 XML timeline edited in Premiere or Resolve back as the cut and removals: deleted stretches become removals, kept ones are restored. With the DaVinci Resolve MCP server connected, import the review timeline into a Resolve project, color the 'Remove' clips, let the editor review, export the timeline as FCP 7 XML, then call 'import_timeline'. Call recordings work too: one file per person becomes a split screen, one gallery recording is split into a camera per tile; Premiere and FCPXML export refuse those layouts for now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atNoFor 'previews': timeline second to take the stills at
cutsNoFor 'set_cuts': the full cut, shots back to back on the timeline
lookNoColor look used by 'render'
nameNoFor 'new': episode name
pathNoFor 'import_timeline': an FCP 7 XML timeline exported from Premiere or Resolve
filesNoFor 'new': explicit media file paths, alone or with folder
forceNoFor 'sync': also re-measure offsets that were set by hand
indexNoFor 'cut': 0-based shot index
looksNoFor 'previews': include one still per color look
stemsNoFor 'render': also write one WAV per person (default true)
actionYesWhat to do
folderNoFor 'new': folder holding one episode's recordings, scanned recursively
formatNoFor 'export': premiere (FCP7 XML, also opens in Resolve) or fcpxml (Final Cut Pro, Resolve)
peopleNoFor 'new': speaker names, or {name, role} (default Host, Guest; without roles the last one is the guest). For 'map': the full people list, with ids to keep and role host or guest; a guest's long answers are held on their camera
reviewNoFor 'export': keep the whole episode with every camera on its own track and the removals in place, marked
sourcesNoPer-source corrections. An offset set here survives later syncs unless force is true
removalsNoStretches cut out of the episode on every camera and mic, in timeline seconds; [] restores everything
range_endNoFor 'map'/'plan': episode end on the timeline, null for automatic
source_idNoFor 'cut': camera source id to use for that shot
session_idNoSession id returned by 'new' (every action except new/list)
range_startNoFor 'map'/'plan': episode start on the timeline, null for automatic
speaker_mapNoFor shared-audio shows: diarization label → person id
cut_settingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discloses rich behavioral traits: background jobs return job_id and require polling job_status then 'show'; render skips unchanged work; every render runs validation checks with specific pass/fail criteria; cloud actions need podcli login and Pro; export review produces a marked review timeline. This goes well beyond what structured fields provide.

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?

The description is long, but the complexity of a 17-action, 23-parameter tool justifies the length. It is front-loaded with purpose and workflow, and most sentences add actionable detail rather than filler, though the density could be slightly better organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is remarkably complete: it explains return shapes (session, job_id, validation), background job polling, workflow sequencing, export behaviors, cloud prerequisites, and special layouts for call recordings. An agent has enough context to select actions and invoke the tool correctly.

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 96%, so the baseline is 3, but the description adds meaningful consolidated guidance: it groups mapping fields (people, sources, range_start, range_end, cut_settings, speaker_map, look, removals) as applying to 'map', 'sync', and 'plan', and clarifies that 'render' takes only look and stems. This helps an agent navigate 23 parameters even though the schema already documents them individually.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Edit a full multicam podcast episode', then enumerates the core operations (map, sync, auto-cut, render/export). It clearly distinguishes this tool from sibling tools like export_to_davinci_resolve or manage_assets by framing the entire multicam editing workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides an explicit end-to-end flow ('new' → 'show' → 'map' → 'sync' → 'plan' → 'render' or 'export') and describes when to use each action, including alternatives and conditional branches. It also names prerequisites and consequences, such as re-running 'plan' after mapping changes.

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