Skip to main content
Glama

create_compound_clip

Combine current timeline items into a compound clip, or set fusion_clip to true to create a Fusion clip instead. Use it to group edit elements into one manageable timeline item.

Instructions

Turn items of the current timeline into a compound clip (or into a Fusion clip with fusion_clip=true).

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

Input Schema

NameRequiredDescriptionDefault
nameNo
itemsYes
fusion_clipNo
start_timecodeNo

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?

The annotations already declare this is a non-read-only, non-destructive, closed-world mutation, so the description needn't re-establish safety. It usefully discloses that the source is existing timeline items and that fusion_clip changes the resulting clip type, but it omits what happens to the source items, where the new clip lands, and whether the operation is undoable — meaningful gaps for a timeline mutation.

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?

A single sentence, front-loaded with the primary action and closing with the one mode flag that changes output type. No filler or redundant restatement of the title.

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?

This is a mutation tool with four parameters at 0% schema coverage and no output schema, yet the description covers only one sentence. Half the parameters, the destination of the created clip, and the effect on the original timeline items go unaddressed, which is too thin for the tool's complexity.

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 description coverage is 0%, so the description must carry the burden and only partly does: it explains that 'items' refers to timeline items and that 'fusion_clip' toggles Fusion output. The 'name' and 'start_timecode' parameters are left entirely unexplained in both schema and description.

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 and resource: 'Turn items of the current timeline into a compound clip', and even names the variant mode via fusion_clip=true. It does not distinguish itself from similarly named siblings such as create_multicam_clip or create_stereo_clip, so an agent choosing among the create_*_clip tools still has to infer the boundary.

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?

The phrase 'items of the current timeline' implicitly anchors when the tool applies, and the fusion_clip aside clarifies one branch of usage. There is no explicit when-not guidance, no prerequisites (selection state, target bin), and no comparison to the sibling clip-creation tools.

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