Vibie MCP

filmcraft_export_sequence

Export the active FilmCraft sequence to video using hardware or software encoders. Set output path, preset, range, and acceleration to produce final renders.

Instructions

Renders and exports the active FilmCraft sequence to video using hardware or software encoders.

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": {
      "outputPath": "<outputPath>"
    },
    "name": "filmcraft_export_sequence"
  }
}

Input Schema

Name	Required	Description	Default
`preset`	No	Export preset format	h264_youtube
`outputPath`	Yes	Target file destination (e.g. 'C:/Renders/FinalCut.mp4')
`exportRange`	No	Render range	entireSequence
`hardwareAcceleration`	No	Use GPU hardware encoder (NVENC on Windows/NVIDIA, VideoToolbox on macOS)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It mentions hardware or software encoders but omits important traits: whether outputPath is overwritten, permission requirements, expected duration, hardware fallback behavior, and whether the sequence must be active and saved.

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 front-loaded sentence with no wasted words. It gets directly to the 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?

Although the schema fully documents parameters, there are no annotations and no output schema. For a write/export operation, the description leaves out critical context such as file overwrite behavior, active-sequence requirements, and failure modes.

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 description coverage is 100%, so all four parameters are already documented in the schema. The description adds only a general reference to hardware/software encoders and does not contribute meaning beyond that.

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 states a specific verb and resource: renders and exports the active FilmCraft sequence to video. It clearly distinguishes this from sibling tools like filmcraft_export_markers or filmcraft_capture_frame, which do not produce a full sequence video.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor does it state prerequisites such as requiring an active sequence. Usage is only implied by 'active FilmCraft sequence.'

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