Skip to main content
Glama
Sign In

switch

by ai.switchapp
OverviewDiscussionsAdmin

Capture Editor Assets

capture_editor_assets
Idempotent

Capture a fixed state of the real current production Switch Editor into your Editor project. The default state is an honest baseline capture of the full Editor, its sections, scroll pages, and rendered controls; it has no fabricated click transition. States with a configured interaction add a before PNG, real button-transition WebM, and after PNG. Each manifest records which part of the Editor the state belongs to and the known unavailable or hidden surfaces so missing features are never presented as captured. Populated states require a real library image or video already attached. It uses the live Editor DOM in an isolated read-only browser, not generated or recreated UI, and charges no generation credits. State workflow_screen_record is the screen-record workflow: a timed WebM of the real Editor with a visible cursor that opens the Assets tray, types prompt_text into the prompt box and rests on Send without sending; it fills the tray with a real picture and clip from the library first (real-tray-assets).

Input Schema

NameRequiredDescriptionDefault
stateYesThe real Editor panel or menu state to open before capture.
fill_trayNoreal-tray-assets: before capturing any state, put the newest real picture and clip from your library in the project tray if it has none. Always on for workflow_screen_record.
project_idYes
prompt_textNoworkflow_screen_record only. The words typed into the prompt box on camera, up to 160 characters.
record_secondsNoworkflow_screen_record only. How long the cursor rests on Send at the end, 3 to 12 seconds, default 6.
include_controlsNoDefault true. Also capture every rendered interactive control, including controls reached by scrolling, as a named asset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed4 schema fields changed
    • addedInput schema / properties / fill_tray
      Added value: +{
+  "description": "real-tray-assets: before capturing any state, put the newest real picture and clip from your library in the project tray if it has none. Always on for workflow_screen_record.",
+  "type": "boolean"
+}
    • addedInput schema / properties / prompt_text
      Added value: +{
+  "description": "workflow_screen_record only. The words typed into the prompt box on camera, up to 160 characters.",
+  "type": "string"
+}
    • addedInput schema / properties / record_seconds
      Added value: +{
+  "description": "workflow_screen_record only. How long the cursor rests on Send at the end, 3 to 12 seconds, default 6.",
+  "type": "number"
+}
    • changedInput schema / properties / state / enum
      Previous value: -[
-  "default",
-  "media_assets",
-  "auto_clean",
-  "editor_project",
-  "editor_design_basic",
-  "editor_design_hsl",
-  "editor_design_vintage",
-  "editor_design_curves",
-  "editor_design_color_wheel",
-  "editor_design_mask",
-  "editor_layers",
-  "editor_audio",
-  "editor_renders",
-  "editor_variables",
-  "editor_history",
-  "editor_comments",
-  "editor_text_basic",
-  "editor_text_effects",
-  "editor_captions_auto",
-  "editor_captions_templates",
-  "editor_captions_packaging",
-  "editor_captions_lyrics",
-  "editor_captions_manual",
-  "editor_captions_emojis",
-  "web",
-  "workspace_storyboard",
-  "workspace_code",
-  "workspace_comps",
-  "record",
-  "captions_menu",
-  "keyboard_shortcuts",
-  "export",
-  "layout",
-  "preview_social",
-  "preview_quality",
-  "timeline_linkage",
-  "timeline_preview_options",
-  "timeline_transition",
-  "timeline_add_track",
-  "help"
-]New value: +[
+  "default",
+  "media_assets",
+  "auto_clean",
+  "editor_project",
+  "editor_design_basic",
+  "editor_design_hsl",
+  "editor_design_vintage",
+  "editor_design_curves",
+  "editor_design_color_wheel",
+  "editor_design_mask",
+  "editor_layers",
+  "editor_audio",
+  "editor_renders",
+  "editor_variables",
+  "editor_history",
+  "editor_comments",
+  "editor_text_basic",
+  "editor_text_effects",
+  "editor_captions_auto",
+  "editor_captions_templates",
+  "editor_captions_packaging",
+  "editor_captions_lyrics",
+  "editor_captions_manual",
+  "editor_captions_emojis",
+  "web",
+  "workspace_storyboard",
+  "workspace_code",
+  "workspace_comps",
+  "record",
+  "captions_menu",
+  "keyboard_shortcuts",
+  "export",
+  "layout",
+  "preview_social",
+  "preview_quality",
+  "timeline_linkage",
+  "timeline_preview_options",
+  "timeline_transition",
+  "timeline_add_track",
+  "help",
+  "workflow_screen_record"
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / include_controls / description
      Previous value: -"Default true. Also capture every visible button, input, and selector as a named asset."New value: +"Default true. Also capture every rendered interactive control, including controls reached by scrolling, as a named asset."
    • changedInput schema / properties / state / enum
      Previous value: -[
-  "default",
-  "assets",
-  "auto_clean",
-  "hyperframes_project",
-  "hyperframes_details",
-  "hyperframes_adjust",
-  "hyperframes_vintage",
-  "hyperframes_text",
-  "hyperframes_captions",
-  "hyperframes_skills",
-  "hyperframes_blocks",
-  "hyperframes_guide",
-  "web",
-  "export",
-  "layout"
-]New value: +[
+  "default",
+  "media_assets",
+  "auto_clean",
+  "editor_project",
+  "editor_design_basic",
+  "editor_design_hsl",
+  "editor_design_vintage",
+  "editor_design_curves",
+  "editor_design_color_wheel",
+  "editor_design_mask",
+  "editor_layers",
+  "editor_audio",
+  "editor_renders",
+  "editor_variables",
+  "editor_history",
+  "editor_comments",
+  "editor_text_basic",
+  "editor_text_effects",
+  "editor_captions_auto",
+  "editor_captions_templates",
+  "editor_captions_packaging",
+  "editor_captions_lyrics",
+  "editor_captions_manual",
+  "editor_captions_emojis",
+  "web",
+  "workspace_storyboard",
+  "workspace_code",
+  "workspace_comps",
+  "record",
+  "captions_menu",
+  "keyboard_shortcuts",
+  "export",
+  "layout",
+  "preview_social",
+  "preview_quality",
+  "timeline_linkage",
+  "timeline_preview_options",
+  "timeline_transition",
+  "timeline_add_track",
+  "help"
+]
  5. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare non-destructive and idempotent, but the description adds substantially more: it charges no generation credits, runs in an isolated read-only browser against the live DOM, records unavailable/hidden surfaces in the manifest so missing features are never misrepresented, and requires a real attached image/video for populated states. This is exactly the extra behavioral context the annotations cannot convey.

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 purpose and default behavior are front-loaded in the first sentence, and all remaining sentences carry real information. However, some sentences are long run-ons and the workflow_screen_record passage is dense enough that trimming would help.

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?

For a 6-parameter tool with no output schema, the description covers the capture lifecycle, the state taxonomy, the asset-requirement precondition, and the manifest contents. That is nearly complete, though it could more explicitly tie parameters to states.

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 83%, so the schema already documents state, fill_tray, prompt_text, record_seconds, and include_controls. The description adds flavor (real-tray-assets, resting on Send without sending) but largely restates what the schema properties already say, so it earns only the baseline 3.

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 (capture) plus the resource (a fixed state of the real production Switch Editor into your Editor project), and immediately distinguishes itself from read/generate siblings by emphasizing real DOM versus generated UI. An agent can tell this apart from get_editor_project or export_editor_project without opening a 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?

Explains that the default state is a baseline capture, that configured-interaction states add PNG/WebM/PNG, that populated states require a pre-attached library asset, and details the workflow_screen_record case. It gives clear context for which state to pick but never explicitly names a sibling alternative or an exclusion condition.

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