Skip to main content
Glama

rapid_trim

Batch trim clips to a specified maximum duration to create fast-paced montages. Optionally trim from start, end, or center.

Instructions

Batch trim clips to a maximum duration for fast-paced montages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filepathYesPath to FCPXML file
max_durationYesMaximum clip duration (e.g., '2s', '00:00:02:00')
min_durationNoMinimum clip duration (optional)
keywordsNoOnly trim clips with these keywords
trim_fromNoWhere to trim fromend
output_pathNoOutput path (default: adds _modified suffix)
Behavior2/5

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

With no annotations, the description should disclose key behaviors. However, it only states it trims clips to a max duration, without mentioning whether it modifies the original file or creates a copy (though the output_path param hints at the latter). It also does not describe what happens to clips not meeting max_duration or how min_duration interacts.

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?

The description is a single sentence that efficiently conveys the purpose and context. No wasted words, front-loaded with action and resource.

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 6 parameters and no output schema, the description is too minimal. It lacks explanation of how multiple clips are selected (e.g., all or filtered by keywords), the effect of min_duration, the default trim_from behavior, and whether the operation is destructive or creates a new file.

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?

Input schema has 100% coverage with clear descriptions for all 6 parameters. The description adds context about batch operation and fast-paced montages but does not provide additional meaning beyond the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'batch trim clips to a maximum duration for fast-paced montages', specifying the verb (batch trim), resource (clips), and context (fast-paced montages). This differentiates it from sibling tools like trim_clip (likely single clip) and find_long_clips (detection only).

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 description implies usage for fast-paced montages but provides no explicit guidance on when to use this tool versus alternatives like trim_clip or find_long_clips. No exclusions or scenarios are mentioned.

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