Skip to main content
Glama

Add clip

add_clip

Place media on the timeline. Without start it is appended to the end of the main track. Picks/creates a free track automatically. With float, an image or video goes over the picture as its own layer instead (logo, product shot, screenshot, sticker): at its real size up to 60% of the frame, at start (default 0), on a track above the footage so nothing is pushed along. Position it with transform.

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": {
      "mediaId": "<mediaId>"
    },
    "name": "add_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
inNosource in-point (s)
fitNo
cropNofractions 0–1
nameNo
textNoText style
floatNolayer it over the picture
labelNocolour label shown on the timeline; null removes it
speedNo0.1–16; changing speed keeps the source span
startNotimeline start (s)
fadeInNo
volumeNo0 = mute, 1 = original, up to 4
fadeOutNo
filtersNobrightness -1..1 (0), contrast 0..3 (1), saturation 0..3 (1), blur px
mediaIdYes
opacityNo
overlapNowith trackId: newTrack (default) layers it on a new track if the spot is taken; insert drops it in between the clips nearest start and closes the track up
trackIdNo
durationNotimeline duration (s)
projectIdNoProject to act on (default: the open one)
transformNox/y: offset in project pixels from canvas center (+y is down). scale: 1 = fit. rotation: degrees

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation. The description adds real value beyond them: automatic track selection/creation, the fact that the float layer sits above footage so 'nothing is pushed along', the 60% frame size cap, and the start default of 0. It does not cover failure behavior, what is returned, or how it interacts with existing clips when a spot is taken (that detail lives only in the overlap schema field).

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?

Front-loaded with the core action, then defaults, then the float special case with parenthetical examples. Sentences are dense but each carries a distinct rule; only the long float sentence verges on packing too many clauses (size cap, start default, stacking behavior) into one line.

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 20-parameter mutation tool with nested text/filter/transform objects and no output schema, the description covers the primary modes well but says nothing about what the call returns or produces, and most optional parameters are handled only by the schema. Adequate but not complete for this complexity level.

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 coverage is 65%, so the baseline is around 3. The description clarifies the semantics of start (omitted = append), float (overlay layer, default start 0), and transform (positioning), which is genuinely useful. But with 20 parameters it leaves the text styling block, filters, crop/fit, speed, volume, fades, and trackId/overlap modes entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'Place media on the timeline.' It immediately distinguishes this from siblings like add_text or add_effect by scoping to media placement, and it further splits its own two modes (append vs. float overlay) so an agent knows exactly which behavior it is requesting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use conditions: omit start to append, set float for logos/product shots/screenshots/stickers layered over footage, and use transform to position the overlay. It does not name competing siblings (e.g., add_text for text, add_html_overlay for HTML, add_music for audio beds), so routing to the right tool still requires inference from the sibling list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources