Move a clip to a new timeline position by specifying track type, track index, clip index, and new start or end time in seconds.
Move a clip to a new position on the timeline
| Name | Required | Description | Default |
|---|---|---|---|
| endTime | No | New end time in seconds | |
| clipIndex | Yes | Clip index on that track | |
| startTime | No | New start time in seconds | |
| trackType | Yes | Track type | |
| trackIndex | Yes | Track index |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a mutation, but does not say whether moving the clip ripples adjacent clips, overwrites existing timeline content, requires specific permissions, or what happens if endTime is omitted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted words. It is as concise as possible while still stating the core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 5-parameter mutation tool with no annotations, no output schema, and several related sibling tools, the description is incomplete. It does not explain side effects, constraints, return behavior, or how this differs from move_clip_to_track and other clip-positioning tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameter meanings are already documented in the schema. The description adds no additional semantics beyond the generic phrase 'new position,' so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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' on the timeline. That is clearer than a tautology, but it does not distinguish this operation from siblings like move_clip_to_track, slide_clip, or slip_clip, and 'position' remains ambiguous between time placement and track placement.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit guidance on when to use this tool versus alternatives. An agent must infer from the schema that it sets start/end times for an existing clip rather than moving it to another track or sliding its content.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.