/runway

Natural-language entrypoint for Runway. Interpret the request, keep the user's constraints (ratio, duration, model, references), and treat the live Runway MCP tool descriptions as the source of truth for parameters and defaults.

Usage

/runway <natural language request>

Examples

/runway Make a cinematic hero image of a glass water bottle on wet slate, 16:9
/runway Animate this product shot — slow push-in, 5s, 9:16
/runway Remove the person in the left background of this clip, keep everything else
/runway Expand this vertical video to 16:9
/runway Turn https://example.com/product into a 15s marketing video
/runway Localize this ad into Spanish
/runway Write a 30s upbeat synth track for a launch video
/runway Show my recent generations
/runway How many credits do I have left?

Routing

• One image → generate_image.
• Video from text, or animate an image → generate_video (pass the image as startFrame). Restyle or transform a whole video → generate_video with referenceVideo.
• Targeted edit of existing footage ("change only X, keep everything else") → edit_video.
• Change a video's aspect ratio (uncrop / outpaint) → expand_video.
• Multi-scene story from one prompt → generate_multishot_video.
• Marketing video from a product URL or product image → generate_product_marketing_video.
• Translate an existing ad into another language → localize_ad.
• Music → generate_music. Sound effect → generate_sound_effect. Text-to-speech → generate_speech.
• Cleanup and finishing → remove_image_background, remove_video_background, upscale_image, upscale_video, convert_video_to_hdr.
• Saved Runway workflows → list_workflows, get_workflow, run_workflow; author with create_workflow / save_workflow_version / validate_workflow_graph. Read runway://docs/workflows/* resources first.
• Library, account, credits → list_recent, whoami, list_workspaces, show_plans_and_credits.

Media inputs

• A public HTTPS URL or a Runway-hosted URL can be passed directly.
• A local file must be uploaded first: call init_upload, PUT the bytes to the returned URL(s), then complete_upload, and use the returned asset URL.
• When an image came from a previous Runway tool call, prefer passing its taskId over copying a long signed URL.
• Preserve every supplied reference and the role the user gave it (start frame, end frame, style reference, source video).

Async results

Generation tools return immediately with a task ID. Tell the user generation is in progress; when an inline viewer is available it polls on its own. Otherwise check with get_task at a sensible interval — do not busy-loop.

Do not turn a simple generation into a multi-step workflow. Do not invent tool names, model IDs, parameters, or defaults; the MCP tool descriptions and runway:// resources carry the current values. Generations consume Runway credits — confirm before large batches or expensive models.