Skip to main content
Glama

SwitchApp Video Enhanced

enhance_video_prompt

SwitchApp Video Enhanced. Prepare a video prompt using SwitchApp enhancement while keeping your selected model, references, exact quoted words and requested changes. Pass the same shot fields as generate_video. Returns original_prompt, enhanced_prompt and an enhancement_receipt. Inspect the prompt and reference assignments, then pass enhanced_prompt as subject with the receipt and unchanged shot settings to generate_video. Reuses existing spending authorization; this tool performs enhancement only and never starts video generation. Private enhancement instructions stay on the server. generate_video also applies enhancement automatically when no receipt is supplied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoVideo mode. Must be supported by the chosen model (see list_video_models).
audioNoGenerate audio. ON by default on Seedance 2.5 (text, image and reference), on Omni, and on every WAN 3.0 lane (text, image, reference); set false for a silent clip. Models without audio ignore this. See list_video_models for which models generate audio and the max seconds with vs without audio.
modelNoModel id from list_video_models (e.g. kling-v3, seedance-2.0-t2v, wan-3.0-t2v, h3-max-t2v, topaz). Or prefer option_id from list_video_models. MiniMax H3 Max ids: h3-max-t2v, h3-max-i2v, h3-max-r2v (option ids h3max-text / h3max-image / h3max-reference). MiniMax H3 Max Turbo (preview, about twice as fast at half the price, no reference lane): h3-max-turbo-t2v, h3-max-turbo-i2v (option ids h3max-turbo-text / h3max-turbo-image). WAN 3.0 ids: wan-3.0-t2v, wan-3.0-i2v, wan-3.0-r2v (option ids wan30-text / wan30-image / wan30-reference): 720p or 1080p, any whole second 2 to 30, generated audio on by default, image lane takes image_url and an optional end_image_url, reference lane takes up to 10 reference_image_urls and 5 reference_video_urls.
subjectNoThe shot: subject + motion + scene (video needs motion language, e.g. "slow push-in"). WAN 3.0: refer to references by their place ("Image 1", "Video 1"), not by @tags; there is no negative-prompt field, so write exclusions inline as "Avoid: ...". MiniMax H3 Max: put spoken words in double quotes and the character says them lip-synced; name references by place (Image 1, Video 1, Audio 1).
durationNoClip length in seconds, or "auto" to let the model choose. Seedance 2.5 does 4-30s (auto bills the 30s cap up front and refunds the unused seconds); Seedance 2.0 does 4-15s; Switch Video (WAN 2.7) does 5/10/15; WAN 3.0 takes any whole second from 2 to 30; Kling/Switch Video Edit cap at 10; MiniMax H3 Max takes whole seconds 5 to 15 (no auto) — see each model's durations in list_video_models.
image_urlNoRequired for image-to-video / frame-to-frame / motion. Accepts EITHER a Switch asset id (from show_media / list_my_assets / upload_media) OR a public https url. An asset id is resolved server-side, so just pass the id you have — no need to fetch a url first.
option_idNoOptional catalog id from list_video_models (e.g. "kling-image"); use instead of model+mode.
task_typeNoSeedance 2.5 reference mode only: declare what you are doing with the reference clip so the size and length rules are checked immediately instead of failing a minute in. auto = a new take from the references (default), edit = change something inside the clip, extend = continue the clip. Editing and extension inherit the source clip's size, and editing also inherits its length.
video_urlNoRequired for video-edit and upscale (the source clip). Accepts one of YOUR Switch videos — a job id from list_my_videos / get_video_status, or its download_url / view_url — or any publicly downloadable https URL. Switch resolves its own videos for you; no need to scrape a page for the file.
resolutionNoOutput resolution. Defaults to 1080p where the model supports it. 720p is cheaper and faster. 480p is the cheapest. Seedance 2.5 offers 480p, 720p and 1080p on every mode (no 2K/4K). 4K is only on Kling v3 text/image and Kling Omni; Seedance text-to-video is 720p only. MiniMax H3 Max offers 480p and 768p only (its reference lane is 768p only). Each model lists its available resolutions in list_video_models.
aspect_ratioNoe.g. 9:16, 16:9, 1:1. Must be allowed for the model (see list_video_models).
end_image_urlNoEnd frame for frame-to-frame mode.
quoted_creditsNoExact quoted_credits returned by quote_video; used with quote_fingerprint.
quote_fingerprintNoFrom quote_video. Pass with quoted_credits to reject a changed quote before charging.
face_reference_idsNoFace reference asset ids from upload_reference_asset (frame_type "face") — the ONLY way to use a face/likeness reference in video. Each id is verified server-side (your own untouched original + identity verification) before the shot fires or is charged; URLs and generic uploads here are rejected.
enhancement_receiptNoReceipt from enhance_video_prompt. Pass its enhanced_prompt as subject with the same model, settings and references. Prevents duplicate enhancement. Changed/expired receipts fail before generation.
reference_audio_urlsNoSeedance reference/omni only: up to 3 reference audio files to drive synthesized audio. Requires at least one reference image or video. MiniMax H3 Max reference (h3max-reference) also takes up to 3 audio files as conditioning (voice/sound guidance); it generates native audio on every clip regardless.
reference_image_urlsNoGENERIC reference images (products, scenery, outfits, style). Each entry accepts EITHER a Switch asset id (from show_media / list_my_assets / upload_media / get_my_active_references) OR a public https url — asset ids are resolved server-side. Seedance reference/omni accepts up to 9; Kling Omni up to 7. WAN 3.0 reference (option wan30-reference, model wan-3.0-r2v) accepts up to 10; name each one by its place in the prompt ("the woman in Image 1", "the jacket from Image 3"). For Seedance, at least one image or video reference is required. For a person's face/likeness use face_reference_ids instead.
reference_video_urlsNoSeedance reference/omni and WAN 3.0 reference. WAN 3.0 (wan30-reference): up to 5 clips, 15 seconds combined, each at least 16 fps, addressed in the prompt as "Video 1", "Video 2"; the audio inside the clips is not kept. Seedance: reference video clips for motion/style guidance — up to 10 on Seedance 2.5 (clips 2-30s, 30s combined), up to 3 on Seedance 2.0 (see list_video_models for each model's caps). A Seedance video ref can satisfy the required visual anchor. Per the BytePlus guide a video reference is a subject reference: it can carry appearance, identity, motion AND voice timbre. State in the prompt what each asset provides. MiniMax H3 Max reference (h3max-reference): up to 3 clips, each second of reference clip is billed on top of the output seconds (see its notes).
character_orientationNoMotion mode only: follow the character image (default) or the reference video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations are minimal (readOnlyHint false, idempotentHint false), so the description carries the burden. It discloses that it 'performs enhancement only and never starts video generation', reuses existing spending authorization, and keeps private instructions on the server. This goes beyond the annotations and clarifies the tool's side effects without contradiction.

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 description is information-dense and well-structured: it leads with purpose, then flow, then constraints, then the auto-enhancement fallback. It avoids fluff and each sentence adds value, though it is longer than average due to the tool's complexity.

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?

Given the 20-parameter complexity and no output schema, the description covers the key workflow (what it returns, how to use it with generate_video) and important caveats (no generation, spending authorization, private instructions). It doesn't detail all parameter-specific edge cases, but the schema covers those, and the description provides sufficient context for correct invocation.

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 20 parameters. The description adds useful context by instructing to reuse the same shot fields as generate_video, but it doesn't elaborate on individual parameters beyond that. This meets the baseline for high 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 states a specific verb ('Prepare') and resource ('video prompt'), and clearly differentiates itself from generate_video by describing its output (enhanced_prompt + receipt) and its role as an enhancement-only step. It also names the sibling it interacts with, making the purpose unambiguous.

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?

It explicitly instructs to 'Pass the same shot fields as generate_video' and describes the exact follow-up workflow: inspect, then pass enhanced_prompt with receipt to generate_video. It also notes that generate_video applies enhancement automatically when no receipt is supplied, giving a clear when-to-use vs. when-not-to-use distinction.

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.

Resources