Skip to main content
Glama

clip_move

Move a clip to an absolute or relative time and/or another track, optionally overwriting occupied destination space.

Instructions

Move a clip to a new time (to, or relative by seconds) and/or another track ('V3'; linked audio moves by the same track offset). The destination must be empty unless overwrite=true (then whatever is there is cut out).

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>"
    },
    "name": "clip_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNo
toNo
clipYes
trackNo
linkedNo
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 does disclose two valuable traits: linked audio follows the same track offset, and existing content at the destination is 'cut out' when overwrite=true. Beyond that it is silent on permissions, undo/reversibility, what happens if 'to' and 'by' are both provided or neither, and what a successful move 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?

Two dense sentences, front-loaded with the action and scope, with the clarifying constraint placed second where it belongs. No filler, no restatement of the tool name.

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

Completeness4/5

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

For a six-parameter mutation tool with zero annotation coverage and no output schema, the description covers the core behavioral risks: destination collision handling and linked-audio side effects. It stops short of covering argument interaction (to vs by) and the clip/track parameter shapes, which leaves a mutation tool slightly under-specified.

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 is the only source of parameter meaning and it does add real value: it clarifies the 'to' vs 'by' (absolute vs relative) distinction, gives a track format example ('V3'), and explains overwrite's effect. It leaves 'clip' and the 'linked' flag's toggle semantics unaddressed, and never resolves the mutual exclusivity of 'to' and 'by'.

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?

States a specific verb and resource ('Move a clip') plus the two dimensions of movement: time ('to', or relative 'by' seconds) and track ('V3'). This is far more informative than the bare name, but it never explicitly contrasts itself with plausible siblings like clip_trim or clip_update, so an agent must infer the boundary.

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?

The precondition 'The destination must be empty unless overwrite=true' tells the agent how to invoke it safely, which is useful implied guidance. However, there is no statement of when to reach for clip_move versus clip_trim, clip_update, or clips_place, and no note on prerequisites or failure conditions when the destination is occupied and overwrite is false.

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