Skip to main content
Glama

sync_audio_timeline

Attach an authorized local audio file to an exported timeline so the project’s audio matches its video.

Instructions

Attach an authorized local audio file to an exported timeline.

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": {
      "timeline": "<timeline>",
      "audio": "<audio>",
      "output": "<output>"
    },
    "name": "sync_audio_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioYes
outputYes
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, and the description does not contradict them. It adds useful prerequisites beyond the annotations: the audio must be a local file and explicitly authorized, and the target must be an already-exported timeline. It says nothing about what non-idempotency means for repeated calls or what happens to existing audio tracks.

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 redundant wording; the key constraint (authorized local audio) appears early. Its brevity is efficient rather than padded, though it verges on under-specification for a three-parameter mutation tool.

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?

An output schema exists, so return values need not be explained, but the definition leaves all three required parameters undocumented and provides no guidance on idempotency or failure modes. For a non-read-only tool with 0% schema coverage, this is materially incomplete.

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%, so the description carries the full burden and largely fails it. It loosely glosses "audio" (local file) and "timeline" (exported), but "output" — a required parameter — is never described, leaving the agent to guess whether it is a path, a format, or the resulting timeline.

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 uses a specific verb ("Attach") and names both the resource being added (an authorized local audio file) and the target (an exported timeline), so the action is unambiguous. It stops short of differentiating itself from near-siblings such as import_audio, so sibling selection still requires inference.

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 explicit when-to-use guidance, no exclusions, and no named alternative. The only implicit guidance is the word "exported," which hints the timeline must already exist, but an agent is given no rule for choosing this over import_audio.

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