Skip to main content
Glama
Sign In

switch

by ai.switchapp
OverviewDiscussionsAdmin

Render Editor Project

render_editor_project

Render your current persistent Switch Editor project as an MP4 through the Switch render service. Use get_editor_run to follow it to playback and download; the finished render carries renderChecks (black gaps, blank screens, frozen stretches, missing layers, dropped sound, with seconds). Look at it with contact_sheet and frame_at, and never hand it over with open findings without saying so. timeline renders one timeline tab by name or id (that tab becomes the open one); default the open tab. PRICE: A render runs as a short Editor job. Priced per step: each step the Editor agent takes costs the same tokens, charged just before the step. How many steps a job takes depends on the job, and every charge shows in get_editor_run as it happens. Things it makes along the way (a picture, a clip, a voice) cost their own price on top, and some of them wait for your yes with approve_editor_run. Pass quote_only: true first to get the exact price; nothing is made and nothing is charged. To run it (not for a quote) send project_id.

Input Schema

NameRequiredDescriptionDefault
timelineNoWhich timeline tab to render, by name ("30 s") or id (read_editor_timeline lists them). Default: the open tab.
project_idNoThe Editor project id to render, from list_editor_projects.
quote_onlyNotrue answers the price only: nothing is made and nothing is charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / quote_only
      Added value: +{
+  "description": "true answers the price only: nothing is made and nothing is charged.",
+  "type": "boolean"
+}
    • removedInput schema / required
      Removed value: -[
-  "project_id"
-]
  2. Changed1 schema field changed
    • addedInput schema / properties / timeline
      Added value: +{
+  "description": "Which timeline tab to render, by name (\"30 s\") or id (read_editor_timeline lists them). Default: the open tab.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / project_id / description
      Added value: +"The Editor project id to render, from list_editor_projects."
  4. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that a render is a priced multi-step Editor job with per-step charges, that artifacts incur separate costs, that some steps block on approve_editor_run, and that quote_only produces a free price quote. It also describes renderChecks contents, which is valuable behavioral detail for a non-readOnly, openWorld tool.

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 and follow-up workflow, then the pricing block. The pricing section is long and somewhat repetitive (per-step cost is explained twice in different words), but each sentence carries distinct information not available in structured fields.

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

Completeness4/5

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

With no output schema, the description compensates well by explaining renderChecks and the get_editor_run follow-up path. It is slightly incomplete about what the immediate return value looks like (job id? run id?), but overall an agent has enough to call it correctly.

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 three parameters and their defaults. The description mostly restates those semantics, adding only the sequencing rule that quote_only should be tried first and that project_id is what actually triggers a run; that is useful but modest marginal value.

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, resource, and output format: renders the current persistent Switch Editor project to MP4 via the Switch render service. It also scopes the timeline variant precisely and is distinguishable from siblings like export_editor_project or aftereffects_render by naming the Editor project/render service.

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?

Gives clear workflow context: follow with get_editor_run, inspect with contact_sheet and frame_at, surface open findings, and pass quote_only:true before running. It does not explicitly state when NOT to use it versus export_editor_project or stitch_in_editor, so it stops short of full alternative routing.

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

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