Skip to main content
Glama
Sign In

switch

by ai.switchapp
OverviewDiscussionsAdmin

Run Editor Agent

run_editor_agent
Destructive

Tell your Switch Editor agent to build or revise the persistent editable project. It can author scenes, layers, variables, files, motion, and narration plans through the real HyperFrames project workspace. Pass workflow to run one of the eleven named editor workflows by id (proof-open, voice-narration, screen-record, real-tray-assets, prompt-breakdown-card, word-captions, beat-and-hits, hard-cut-pacing, credit-card, one-word-cta, long-form-retention-cut for a podcast or talking head into a finished vertical clip); the prompt then carries the creator's specifics and may be omitted to use the workflow's own sentence. PRICE: 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
promptNoWhat to build or change, in plain words. Optional when workflow is set.
workflowNoOptional named editor workflow to run; its recipe is added to the prompt.
project_idNoThe Editor project id, 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 / project_id / description
      Added value: +"The Editor project id, from list_editor_projects."
  3. Changed3 schema fields changed
    • addedInput schema / properties / prompt / description
      Added value: +"What to build or change, in plain words. Optional when workflow is set."
    • addedInput schema / properties / workflow
      Added value: +{
+  "description": "Optional named editor workflow to run; its recipe is added to the prompt.",
+  "enum": [
+    "proof-open",
+    "voice-narration",
+    "screen-record",
+    "real-tray-assets",
+    "prompt-breakdown-card",
+    "word-captions",
+    "beat-and-hits",
+    "hard-cut-pacing",
+    "credit-card",
+    "one-word-cta",
+    "long-form-retention-cut"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "prompt"
-]New value: +[
+  "project_id"
+]
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true, but the description adds the crucial beyond-annotation behavior: per-step token charging before each step, variable cost depending on job, extra charges for generated assets, and gated assets awaiting approve_editor_run. It also clarifies that quote_only makes and charges nothing, which resolves the ambiguity an agent would face with a destructive 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?

The build/revise purpose and workflow mechanism are front-loaded, and the PRICE block carries real behavioral weight rather than filler. It is dense and slightly redundant, repeating the quote_only 'nothing is made and nothing is charged' idea already present in the schema and earlier in the paragraph, which costs it a bit of tightness.

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 destructive, open-world, non-idempotent agent tool with no output schema, the description covers the full call lifecycle: how to pick a workflow, how to get a price without side effects, the charging model, gated asset approval via approve_editor_run, and the requirement to send project_id to actually run. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds value: it explains that workflow selects one of eleven named recipes and even clarifies the intended use of long-form-retention-cut (podcast/talking head into a vertical clip), and that prompt carries the creator's specifics and may be omitted when workflow is set. This goes beyond the enum descriptions provided in the schema.

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?

Specific verb (build or revise) and resource (persistent editable project via the HyperFrames workspace), plus an explicit list of what it can author: scenes, layers, variables, files, motion, narration plans. An agent can tell this apart from siblings like edit_editor_timeline or create_editor_project because this one describes the agent-driven job model rather than a single timeline edit.

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

Usage Guidelines5/5

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

Explicitly states how to select a workflow by id, that prompt may be omitted to use the workflow's own sentence, that quote_only must be passed first for pricing, and that project_id is required to actually run. It also routes to approve_editor_run for gated assets and get_editor_run for live charges, so the when-to-use and when-to-look-elsewhere paths are clear.

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