ClipFlux

Export the video

export_video

Exports a made video to its final MP4, exactly as the Studio's Export does: the video's current Studio timeline (with any edits) is rendered, in a few minutes. The ClipFlux card follows the export and then plays the finished video with a download link. Free accounts' exports carry a small ClipFlux mark, as on the site. Call it when the user wants the finished file, or before posting.

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": {
      "videoId": "<videoId>"
    },
    "name": "export_video"
  }
}

Input Schema

Name	Required	Description	Default
`videoId`	Yes	The video id, from draft_video, list_my_videos or get_video.
`resolution`	No	Only for a long (16:9) video on the Pro or Studio plan, when the user asks for 1440p. Leave it out for 1080p.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare the safety profile (not read-only, not destructive, closed-world); the description adds real behavioral context beyond that: the render takes a few minutes, a ClipFlux card follows the export and then plays the result with a download link, and free accounts get a watermark. These are exactly the side effects and async traits an agent needs before invoking.

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?

Front-loaded with the action and outcome; the 'exactly as the Studio's Export does' clause is a slight redundancy but anchors the mental model. Four sentences, each mostly earning its place.

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

Completeness5/5

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

No output schema exists, and the description compensates by explaining the post-call flow (card follows export, finished video plays with download link) and the watermark caveat. For a two-parameter async render tool, nothing an agent needs in order to call it correctly is missing.

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 both videoId and resolution are already documented with provenance and the 1440p-only-on-Pro/Studio rule. The description adds only the indirect note that the current timeline with edits is what gets rendered, which is useful but not parameter-level detail.

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?

States a specific verb and resource ('Exports a made video to its final MP4') and scopes it to rendering the current Studio timeline, which clearly separates it from edit_video, edit_draft and draft_video. An agent can tell this is the terminal render step without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call it when the user wants the finished file, or before posting" gives an explicit trigger and implicitly positions it ahead of post_video/prepare_post. It does not name an alternative tool or state when not to call it (e.g., while edits are still pending), so it falls just short of full routing guidance.

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

All ClipFlux tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?