Skip to main content
Glama

move_clip

Moves a timeline clip and its linked audio to a new start time in seconds, optionally onto another track or inserted at the new position.

Instructions

Move a clip (and its linked audio) to a new time and optionally another track.

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": {
      "clip": "<clip>",
      "position": "<position>"
    },
    "name": "move_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYesTimeline clip id (from list_timeline)
trackNo
insertNo
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app
positionYesNew start, in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the write scope is already known. The description adds real value by disclosing the side effect that linked audio is moved too, but says nothing about the ripple/overwrite consequences of the undocumented `insert` flag, what happens on out-of-range positions, or whether the move is reversible.

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 front-loaded sentence with no filler; the core action leads and the linked-audio caveat follows immediately. Nothing could be cut without losing 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 five-parameter mutation tool with no output schema and only two annotation hints, the definition covers the headline behavior but leaves the agent guessing about the ripple semantics of `insert` and about failure modes. Adequate to call correctly in the simple case, thin for edge cases.

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 60%: clip, project, and position are documented in the schema, and the description only reinforces that `track` is optional. The `insert` boolean, arguably the highest-consequence parameter here (ripple insert vs. overwrite), is left completely undefined 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?

"Move a clip ... to a new time and optionally another track" names a specific verb and resource and adds a scope detail worth knowing (linked audio moves with the clip). It is clearly distinguishable from trim_clip and split_clip, though it never names those siblings explicitly.

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?

Usage is only implied by the verb: an agent can infer this is the tool for repositioning an existing clip rather than resizing or cutting it. There is no explicit when-to-use, no when-not-to-use, and no pointer to trim_clip/split_clip as alternatives for other kinds of timeline edits.

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