Skip to main content
Glama

compound_create

Nest timeline clips into a compound or Fusion clip to group edits and reuse them as a single timeline item.

Instructions

Nest timeline clips into a compound clip (kind='compound') or a Fusion clip (kind='fusion').

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

Input Schema

NameRequiredDescriptionDefault
kindNocompound
nameNo
clipsYes
start_timecodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only states that clips are nested into a compound or Fusion clip. It does not disclose permissions, side effects, whether existing clips are moved or altered, or what the operation returns.

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?

The definition is a single front-loaded sentence with no redundant wording. It communicates the core action and kind options efficiently.

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 creation tool with four parameters, no annotations, no output schema, and zero schema descriptions, the description is too sparse. It omits behavioral details, most parameter meanings, and any return-value context.

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 must compensate, but it only clarifies the kind parameter by naming 'compound' and 'fusion'. It says nothing about name, clips, or start_timecode, leaving three of four parameters undocumented.

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 gives a specific verb ('Nest') and resource ('timeline clips into a compound clip or a Fusion clip'), and it distinguishes the two kind variants. It does not differentiate this tool from siblings such as timeline_create or multicam_create, so it falls short of a 5.

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?

The description explains the kind options but gives no explicit when-to-use or when-not-to-use guidance. It never mentions alternatives like timeline_create or multicam_create, leaving the agent to infer selection criteria.

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