Skip to main content
Glama

generate_ab_roll

Create a documentary-style A/B roll edit alternating between A-roll main content and B-roll cutaways. Specify keywords for each, segment durations, total length, and whether to start with A or B. Optionally add cross-dissolve transitions.

Instructions

Create documentary-style A/B roll edits alternating between main content and cutaways

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filepathYesSource FCPXML with clips
output_pathYesWhere to save A/B roll edit
target_durationYesTotal duration (e.g., '3m', '00:03:00:00')
a_keywordsYesKeywords for A-roll (main content, interviews)
b_keywordsYesKeywords for B-roll (cutaways, visuals)
a_durationNoDuration of each A-roll segment5s
b_durationNoDuration of each B-roll cutaway3s
start_withNoWhich roll to start witha
add_transitionsNoAdd cross-dissolves
Behavior2/5

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

With no annotations, the description carries the full burden. It only states the high-level behavior (alternating A/B roll edits) but omits important details such as how clips are selected, whether the original timeline is modified, or any side effects. The agent lacks critical behavioral context.

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

Conciseness4/5

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

The description is a single, concise sentence that gets to the point. However, given the tool's complexity (9 parameters), a bit more detail would be justified without sacrificing conciseness.

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?

Considering the tool has 9 parameters, 5 required, no output schema, and no annotations, the description is insufficient. It does not explain the output format, preconditions, or how parameters affect the result. The agent is left with many unknowns.

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 coverage is 100%, so the schema already documents all parameters and their types. The description adds no additional meaning or usage hints beyond the schema, such as how keywords interact or how durations are interpreted. Baseline score applies as no extra value is provided.

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 tool creates A/B roll edits alternating between main content and cutaways, with a documentary-style focus. It distinguishes from siblings like 'generate_montage' but could better differentiate from 'auto_rough_cut' and other similar tools.

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. The description does not mention prerequisites, when not to use, or context for choosing this over sibling tools like 'generate_montage' or 'auto_rough_cut'.

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