Skip to main content
Glama

reorder_clips

Rearrange clips in a Final Cut Pro timeline by moving them to a specific position: start, end, a timecode, or after another clip. Includes ripple edit option.

Instructions

Move clips to a new position in the timeline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filepathYes
clip_idsYesClips to move
target_positionYes'start', 'end', timecode, or 'after:clip_id'
rippleNo
output_pathNo
Behavior2/5

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

With no annotations, the description should fully disclose behavior. It omits key aspects like ripple effects, in-place modification vs. new file, and implications of optional parameters. The minimal phrase 'move clips to a new position' is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (10 words), which is concise but not optimally structured. It could be expanded with front-loaded key details to improve usefulness without becoming verbose.

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

Completeness2/5

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

Given the tool has 5 parameters, no annotations, and no output schema, the description is incomplete. It does not cover required vs. optional parameters, safety (e.g., undoability), or expected return behavior, leaving an agent with significant ambiguity.

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?

The description partially compensates for low schema coverage (40%) by implying the role of clip_ids and target_position. However, it does not explain filepath, ripple, or output_path, leaving gaps that the schema also leaves undocumented.

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 clearly states the action (move clips) and the target (new position in timeline). It is specific enough to distinguish from tools like delete_clips or insert_clip, though it doesn't explicitly differentiate from reorder-like siblings.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as insert_clip, reformat_timeline, or trim_clip. The description lacks context for selection among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DareDev256/fcpxml-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server