Skip to main content
Glama
Sign In
FilmCraft MCP

FilmCraft MCP

by glorybnat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fc_export

Export the active FilmCraft sequence to a specified output path or preset, with format inferred from the file extension or set explicitly. Returns a result object that includes offline-media warnings.

Instructions

Export the active filmCraft sequence. Specify an output path with a format matched to its extension, or pass a preset name. Returns a result object that includes any offline-media warnings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "out": "<out>"
    },
    "name": "fc_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoCustom range end in seconds (requires start).
outYesOutput file path (extension determines format when --format is omitted).
queueNoAdd to the export queue and run it, instead of a direct render.
rangeNoExport range (default: entire sequence).
scaleNoRender at a fraction of full frame size (e.g. 0.5 = half resolution).
startNoCustom range start in seconds (requires end).
formatNoExplicit format: h264, hevc, prores, dnxhr, apv, mjpeg, mxf-op1a, mxf-opatom, png, tiff, bmp, gif, wav, aiff, aac.
presetNoExport preset name. Use fc_list_export_presets to discover available presets.
qualityNoQuality 0-100 for formats that support it.
no_audioNoOmit audio from the export.
allow_offlineNoAllow offline media to render as placeholder frames.
gpu_renderingNoGPU rendering mode (default: auto).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.24.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It adds meaningful return context by noting that the result object includes offline-media warnings, but it omits other important traits such as whether existing output files are overwritten, what happens when there is no active sequence, and other failure or permission considerations.

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?

Three sentences, front-loaded with the core operation and followed by format/preset guidance and return-value context. Every sentence contributes useful information without redundant wording.

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

Completeness3/5

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

For a 12-parameter export tool with no annotations and no output schema, the description covers the core purpose and notes that offline-media warnings may be returned. It is still thin on operationally important behavior such as overwrite semantics, queue execution, and active-sequence prerequisites.

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 the schema already documents all 12 parameters. The description clarifies the central out/format/preset relationship, but this largely restates what the schema says about extension-based format inference and preset discovery.

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 states a specific verb and resource: "Export the active filmCraft sequence." This makes the operation clear and distinct from sibling tools like fc_import or fc_inspect, though it does not explicitly name fc_render_frame as the alternative for single-frame rendering.

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?

It gives useful selection guidance: specify an output path with a format matched to its extension, or pass a preset name. However, it does not explain when to use this tool versus fc_render_frame, nor when to prefer queue versus direct render, leaving those choices implicit.

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

Deploy Server

Other Tools