switch

Export Editor Project

export_editor_project

Export an Editor project to an MP4 the way the Export button does: the row of clips on the video tracks is joined (cuts, sound shapes, frames) with every sound clip on the audio tracks mixed in at its own second with its volume and fades, then the text layers, captions, logos, pictures, motion blocks, the look and the sound settings are rendered on top. Options as the Export menu offers them: resolution 480p / 720p / 1080p, frame rate 24 / 25 / 30 / 50 / 60, quality standard or high (AI ultra HD), bit rate, sound on or off, the frame ratio. Charged the same as pressing Export (a join and a render). Answers at once with an export id; call get_editor_export until it says complete with the file link. The file also lands in your library and in the project's Renders panel.

Input Schema

Name	Required	Description
`fps`	No	Default: the project's fps (project_settings), else 30.
`name`	No	The file name, without extension.
`ratio`	No	The frame: original keeps the first clip's own frame. Default: the project's shape (project_settings), else original.
`bitrate`	No	Default Recommended.
`quality`	No	high = the AI ultra HD switch. Default standard.
`timeline`	No	Which timeline tab to export, by name ("30 s") or id (read_editor_timeline lists them). Default: the open tab.
`project_id`	Yes	The Editor project id (list_editor_projects).
`resolution`	No	Default 1080p.
`include_audio`	No	Default true.
`range_end_sec`	No	The Out point in seconds (with range_start_sec).
`range_start_sec`	No	Export only a part of the timeline: the In point in seconds (with range_end_sec). Default: the whole project.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 22, 2026

changedInput schema / properties / fps / description

Previous value: -"Default 30."New value: +"Default: the project's fps (project_settings), else 30."

changedInput schema / properties / ratio / description

Previous value: -"The frame: original keeps the first clip's own frame. Default original."New value: +"The frame: original keeps the first clip's own frame. Default: the project's shape (project_settings), else original."

addedInput schema / properties / timeline

Added value: +{
+  "description": "Which timeline tab to export, by name (\"30 s\") or id (read_editor_timeline lists them). Default: the open tab.",
+  "type": "string"
+}

Changed2 schema fields changedOct 22, 2026

addedInput schema / properties / range_end_sec

Added value: +{
+  "description": "The Out point in seconds (with range_start_sec).",
+  "type": "number"
+}

addedInput schema / properties / range_start_sec

Added value: +{
+  "description": "Export only a part of the timeline: the In point in seconds (with range_end_sec). Default: the whole project.",
+  "type": "number"
+}

AddedOct 13, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that the call consumes credits at the same rate as pressing Export, that it is asynchronous and returns immediately with an id, and that the result additionally lands in the library and the project's Renders panel. Those are exactly the operational details an agent needs and cannot get from structured fields.

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 core action, then options, then cost and async follow-up. The long list of composited elements in the first sentence is dense but earns most of its space by clarifying what is rendered; a few items could be trimmed.

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?

For a mutation-style async tool with no output schema, the description supplies everything missing: the return shape (an export id), the completion mechanism (get_editor_export), the side effects (library and Renders panel), and the billing implication. Nothing an agent needs to invoke it correctly is absent.

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 baseline is 3. The description mirrors the menu options (resolution, fps, quality, bitrate, audio, ratio) but adds only one real clarification beyond the schema, that 'high' equals the AI ultra HD switch; the polling/timeout behavior is not parameter-specific.

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 ('Export') and resource ('Editor project') and then enumerates exactly what gets composited into the MP4. It also names the follow-up sibling get_editor_export, so the agent can place this tool in the pipeline without inspecting schemas.

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?

Explains the flow clearly: call this, get an export id immediately, then poll get_editor_export until complete. It does not explicitly contrast with sibling render_editor_project, which is the one alternative an agent might confuse it with, so it stops short of full when/when-not guidance.

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

All switch 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?