Skip to main content
Glama

Runway MCP Server by useapi.net (third-party)

Create Frames images

runway_create_frames

Generate 1 or 4 images at 1080p with Runway Frames from a required prompt, with up to 3 reference image assets cited as @IMG_1, @IMG_2, @IMG_3, a style preset and an aesthetic range (diversity). runway_create_image is the general image tool (13 models); runway_describe_image turns an image into a starting prompt for this one. Waits up to ~50 s, then returns each image's url and assetId plus the first image inline, the failure reason or the taskId for runway_get_task. Uses credits, or none with exploreMode. POST /frames/create.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text_prompt": "<text_prompt>"
    },
    "name": "runway_create_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoSeed for reproducible results, 1-4294967294; random when omitted.
waitNoWait up to ~50 s for the task to finish (default true); false returns the taskId at once.
emailNoThe Runway account to run it on: its email from runway_list_accounts. Omit it with reference assets (the account that holds them runs the task) or to let the API pick one of your accounts.
styleNoA style preset.
maxJobsNoOverride the account's maxJobs (Runway tasks at once) for this request, 1-10. Default: the account's own setting.
replyRefNoYour own reference id, stored and returned with the task.
replyUrlNoA callback URL the API calls with the task (the runway_get_task shape) when it completes or fails. Default: the replyUrl of your useapi.net account.
diversityNoAesthetic range, 0-5: higher varies the images in a set more. With reference images the value is ignored: 2 is always used; without, nothing is sent when omitted (or 0).
num_imagesNoImages per task: 1 (default) or 4.
exploreModeNoExplore Mode: true spends no credits and runs at lower priority; only for accounts on a Runway Unlimited plan. Omit or false: Credits Mode.
text_promptYesWhat the image shows; cite references as @IMG_1, @IMG_2, @IMG_3.
aspect_ratioNoDefault 16:9.
imageAssetId1NoimageAssetId1, reference image 1 (@IMG_1): an assetId from runway_upload_asset, runway_list_assets or a finished task (runway_get_task artifacts). The task runs on the Runway account that holds the asset.
imageAssetId2NoimageAssetId2, reference image 2 (@IMG_2): an assetId from runway_upload_asset, runway_list_assets or a finished task (runway_get_task artifacts). The task runs on the Runway account that holds the asset.
imageAssetId3NoimageAssetId3, reference image 3 (@IMG_3): an assetId from runway_upload_asset, runway_list_assets or a finished task (runway_get_task artifacts). The task runs on the Runway account that holds the asset.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare non-readonly, open-world, non-idempotent, non-destructive. Beyond that the description discloses the ~50 s wait window, the shape of the return (url + assetId per image, first image inline), the failure path (failure reason or taskId for runway_get_task), credit consumption versus free exploreMode, and that reference assets force the task onto the account that holds them. It even cites the underlying POST /frames/create endpoint.

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?

Purpose and output shape are front-loaded, and every sentence carries usable information (capacity, references, alternatives, timing, returns, cost). The second sentence is a dense run-on that chains return values, failure handling and an HTTP endpoint, which costs a little scannability.

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 15-parameter async generation tool with no output schema, the description covers what is produced, that the first image is returned inline, that failures surface as a reason or a taskId to poll via runway_get_task, the wait default, and the credit/account implications. Nothing an agent needs in order to call or follow up correctly is missing.

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 100% and the schema already documents seed ranges, wait behavior, email-omission-with-reference-assets, diversity being ignored when references are used, maxJobs, replyUrl/replyRef, and exploreMode. The description restates the prompt, the @IMG_1-3 citation convention, style and diversity but adds little the parameters do not already say, so the baseline of 3 is appropriate.

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 and resource ('Generate 1 or 4 images at 1080p with Runway Frames from a required prompt') and immediately names the distinguishing capabilities: reference-image citation, style preset, diversity, and the model name Frames. It also explicitly contrasts with runway_create_image as 'the general image tool (13 models)', so the agent can tell the specialized tool from the general one without opening either schema.

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?

Gives explicit alternatives and the conditions that select them: runway_create_image is the general 13-model image tool, and runway_describe_image is the pipeline for turning an existing image into a starting prompt for this tool. That is a genuine routing rule, not just a list of sibling names.

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