Skip to main content
Glama

auto_sync_audio

Synchronizes video and audio clips by waveform, timecode, in/out points, or markers to align dual-system sound for editing.

Instructions

Sync video and audio clips (dual-system sound) by waveform, timecode, in/out points or markers.

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": "auto_sync_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
channelNoautomatic
sync_modeNowaveform
retain_embedded_audioNo
retain_video_metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare this is a non-destructive, closed-world mutation (readOnlyHint=false, destructiveHint=false), so the safety profile is covered. Beyond that the description says nothing about what actually happens on invocation: whether clips are moved, whether new synced clips are created, what occurs when waveform matching fails, or whether existing in/out points are preserved.

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 front-loaded sentence with no filler; the core action and its modes come first. Its terseness is efficient but is also the source of the gaps noted in other dimensions rather than padding.

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 five-parameter mutation tool with no output schema and zero schema descriptions, this one-sentence description is too thin. An agent cannot learn from it what the optional parameters do, what the result of a sync is, or what conditions must hold for each sync mode to succeed.

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 five parameters, so the description must carry the explanatory load. It only partially does: the enumerated sync methods map to sync_mode, but the 'clips' array, 'channel' (including the 'mix' option), 'retain_embedded_audio' and 'retain_video_metadata' are never mentioned, leaving four parameters undocumented anywhere.

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 and resource ('Sync video and audio clips') plus the domain term 'dual-system sound' and the four supported sync strategies, which is more than enough to tell it apart from siblings like insert_audio_at_playhead or create_multicam_clip. It stops short of explicitly stating what it does NOT do relative to those siblings.

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?

Usage is implied by the phrase 'dual-system sound', which tells an experienced editor this is the tool for matching separately recorded audio to picture. However, there is no explicit when-to-use vs when-not guidance, no named alternative for single-system audio, and no stated prerequisites such as clips needing overlapping timecode or shared markers.

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