Skip to main content
Glama

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

Upload an asset

runway_upload_asset

Upload your own image, video or audio file to a Runway account's assets, for use as an input (an assetId) in runway_create_video, runway_create_image, runway_edit_video_aleph, runway_act_two, runway_lipsync and the other create tools; a generation that uses the asset runs on the account it was uploaded to. Send a public https url or contentBase64 (small files), up to 50 MB here; larger files go to POST /assets directly. Returns the new assetId, its url, name, type and size. POST /assets.

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": {
      "name": "<name>"
    },
    "name": "runway_upload_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public https URL of the file.
nameYesThe asset's name as Runway shows it (the file extension is added from the type).
emailNoThe Runway account email to upload to (runway_list_accounts). Required when you have several Runway accounts; with one it may be left out.
widthNoThe image or video width in pixels (images and videos only).
heightNoThe image or video height in pixels (images and videos only).
mimeTypeNoThe file's type. Default: from the url's answer, else its file extension.
contentBase64NoThe file content, base64-encoded (instead of url).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses the 50 MB ceiling, the alternate endpoint for larger files, and the important consequence that a generation using the asset runs on the account it was uploaded to. It also names the return fields (assetId, url, name, type, size) even though no output schema exists.

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 is front-loaded and every clause carries information, but the middle is a single run-on sentence that enumerates many sibling tool names where a shorter phrase like 'the create tools' would serve. Slight density cost, no wasted content.

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 7-parameter upload tool with no output schema, the description covers inputs, limits, account scoping, and the return shape. It does not mention duplicate/non-idempotent behavior when re-uploading the same file, which the idempotentHint=false annotation implies but does not explain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real selection guidance: use a public https url or contentBase64 for small files, with the size limit clarifying the tradeoff. It does not, however, add meaning for width, height, or mimeType beyond what the schema already documents.

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?

'Upload your own image, video or audio file to a Runway account's assets' gives a specific verb, resource, and accepted media types, and immediately frames the outcome (an assetId consumable by named create tools). This clearly separates it from runway_list_assets, runway_get_asset, and runway_delete_asset.

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 states exactly when to use this tool (to obtain an assetId for runway_create_video, runway_create_image, runway_edit_video_aleph, runway_act_two, runway_lipsync) and when not to (files over 50 MB should go to POST /assets directly). It also steers multi-account callers to runway_list_accounts for the email value.

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