Cancel Editor Run
cancel_editor_runIdempotent
Safely cancel one of your queued, running, or approval-waiting Switch Editor runs without applying a pending revision.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes |
switch
by ai.switchapp
TDQS
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate write (readOnlyHint=false) and idempotent (idempotentHint=true). Description adds 'Safely cancel' and 'without applying a pending revision', providing behavioral nuance beyond annotations. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
One concise sentence, clearly front-loaded with the verb and purpose. No fluff.
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 simple cancel operation with a single parameter, the description covers the main purpose and behavior, but could mention how to obtain run_id or typical usage context. Still, it's fairly complete for its simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds no semantics for the run_id parameter. Schema provides only type string with no description; the description does not mention run_id at all, so it fails to compensate for the 0% schema coverage.
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?
The description clearly states the tool cancels a Switch Editor run, specifies the states (queued, running, approval-waiting), and notes it does not apply a pending revision. The verb 'cancel' and the resource 'editor runs' are specificaint it distinguishes from siblings like approve_editor_run and cancel_my_task.
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?
The description provides clear context for when to use (cancelling editor runs in specific states) and subtly distinguishes from approval by noting it doesn't apply a pending revision. It doesn't explicitly state alternatives or when not to use, but the context is enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation2/5
Several tools occupy nearly identical semantic ground: apply_iphone_realism and apply_ugc both describe casual phone-shot looks, upload_media and upload_reference_asset both accept uploads, and analyze_video overlaps heavily with analyze_video_report. The many apply_* style tools are essentially one tool parameterized by style, so agents can easily select the wrong one.
Naming Consistency4/5
Most tools follow a clear verb_noun snake_case pattern such as generate_image, list_my_videos, get_editor_run, and upscale_video. A few outliers like voice, talking_avatar_video, and video_to_prompt do not use the same verb-first convention, but they are still readable and do not create significant confusion.
Tool Count1/5
At 55 tools, the surface is far beyond what is appropriate for an MCP server; many of these be collapsed or parameterized, especially the 10 apply_* style wrappers and several overlapping upload/status helpers. Even for a broad media platform, this scale forces a huge context window and makes selecting the right tool impractical.
Completeness2/5
The surface covers generation, media display, video analysis, and Editor workflows well, but there are obvious gaps in library lifecycle management: move_asset and create_folder are referenced in tool descriptions without being exposed, and there is no clean way to delete or reorganize media assets. Agents following the descriptions will try to call tools that do not exist.