Skip to main content
Glama

place_clips

Place b-roll, images, music, and sound effects at exact edited-timeline times on chosen tracks, with per-clip duration, ducking, looping, and fade-out controls.

Instructions

Place clips on the timeline at edited-timeline times: b-roll/images on upper video tracks (track 2+), music and sound effects on audio tracks. Standalone extras: duration (images), duckDb (lower music under speech by ~N dB), loop, fadeOut.

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

Input Schema

NameRequiredDescriptionDefault
clipsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It omits any mention of overlap handling, whether placed clips replace or stack, prerequisites (media must be imported first), permissions, or what the response looks like, and the only behavioral signals are the track-default and duckDb dB semantics.

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?

Two dense sentences with zero filler, front-loaded with the core placement rule. The closing "Standalone extras" fragment is terse and jargon-heavy, but every clause carries real information.

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

Completeness3/5

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

For a tool whose single top-level parameter nests eleven properties with no annotations and no output schema, the definition covers track routing, duration, and duckDb, but leaves several parameters and all failure/precondition behavior undocumented. Adequate but with clear gaps for a timeline-mutation tool.

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 compensate, and it partly does: it explains that duration applies only to images, that duckDb lowers music under speech by roughly N dB, and that track 2+ holds upper video. It leaves sourceIn/sourceOut, gainDb, loop, and path unexplained, so the compensation is partial rather than complete.

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 opens with a concrete verb and resource ("Place clips on the timeline") and adds routing rules: b-roll on track 2+, music/SFX on audio tracks. It never names a sibling, so the agent must infer that import_media is the prerequisite and that no other tool places clips.

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?

It gives placement guidance (which kinds of media go on which tracks, default track 2) but no when-to-use/when-not guidance and no named alternative. The agent knows how to place clips but not explicitly why it would choose this tool over import_media or make_captions.

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