Skip to main content
Glama

add_clip

Places a project item on the timeline at a chosen position, overwriting by default or ripple-inserting when insert is enabled.

Instructions

Place a project item on the timeline. Overwrites by default; set insert=true to ripple-insert. The picture goes to track and linked sound to audioTrack.

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

Input Schema

NameRequiredDescriptionDefault
inNoSource in point, in seconds
outNoSource out point in seconds; omit to use the rest of the media
itemYesProject item id (from import_media / inspect_project)
audioNo
trackNoTrack name such as "V1", "V2", "A1"V1
videoNo
insertNo
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app
positionNoTimeline position, in seconds
audioTrackNoAudio destination, e.g. "A1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false and openWorldHint=false, so the disclosure that the operation overwrites existing timeline content by default is genuinely additive and warns the agent of a destructive default. It also explains the picture/sound routing to two different tracks, though it says nothing about what is returned or how conflicts on the target track surface.

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?

Three short sentences, no filler, with the default-overwrite warning front-loaded ahead of the flags and parameter mapping. Every clause carries information the agent needs to call the tool correctly.

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 10-parameter mutation tool with no output schema, the description covers the risky defaults but leaves the audio/video toggles and the return value undescribed. An agent can invoke it, but cannot fully predict what it gets back or what the two boolean switches do.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 70% schema coverage, several parameters (notably audioTrack, audio, and video) carry no schema description at all, and the description compensates by explaining the track/audioTrack split and the insert ripple behavior. The audio and video booleans remain semantically unexplained in both places, which is the main gap.

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 concrete verb and resource ("Place a project item on the timeline"), which clearly separates it from move_clip, trim_clip, and import_media. It does not explicitly name a sibling or state a boundary, but the action-addressing-the-timeline framing is unambiguous.

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?

It gives an explicit decision rule for the most consequential flag: overwrite by default, ripple-insert with insert=true. It stops short of naming alternatives (e.g. move_clip for existing clips) or stating preconditions such as needing imported media first, so situational guidance is incomplete.

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