Skip to main content
Glama

apply_template

Apply a template by mapping clips to named slots, then output an FCPXML file for use in Final Cut Pro.

Instructions

Fill a timeline template with clips and generate FCPXML

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_nameYesTemplate name (intro_outro, lower_thirds, music_video)
clipsYesMap of slot_name -> {src, name, duration} or {asset_id, name, duration}
output_pathYesOutput FCPXML path
fpsNoFrame rate
Behavior2/5

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

No annotations provided, and description lacks behavioral details such as whether it modifies the current timeline, side effects, or output format beyond implying a file is generated.

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?

Single sentence with no redundancy, but could be structured to front-load key verbs and resources.

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 4 parameters (including nested objects) and no output schema, the description is too brief. It does not explain what 'fill a timeline template' means or the expected clip format.

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 coverage is 100%, so baseline is 3. Description does not add meaning beyond schema; it omits explanation of nested clips structure.

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 the verb 'fill' and 'generate' and the resources 'timeline template' and 'FCPXML'. It distinguishes from sibling tools like list_templates or other timeline manipulation 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 on when to use this tool versus alternatives like auto_rough_cut or insert_clip. No prerequisites or exclusions 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