Skip to main content
Glama

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

Upscale a video to 4K (Topaz)

runway_upscale_video

Upscale any video asset up to 40 s to 4K with Topaz, keeping its aspect ratio (a 1280x720 source becomes 4096x2304): a video from runway_create_video or any other Runway task, or your own upload. The account that holds the asset pays: 2 credits per second, or none with exploreMode on an Unlimited plan. runway_upscale_gen4 is the older 4K upscale for Gen-4 and Gen-3 Alpha (Turbo) videos only. Waits up to ~50 s, then returns the video url and assetId, the failure reason or the taskId for runway_get_task. POST /videos/upscale.

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

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the task to finish (default true); false returns the taskId at once.
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.
exploreModeNoExplore Mode: true spends no credits and runs at lower priority; only for accounts on a Runway Unlimited plan. Omit or false: Credits Mode.
videoAssetIdYesvideoAssetId, the video to upscale (up to 40 s): 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.8/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint false, destructiveHint false, idempotentHint false, openWorldHint true) by disclosing cost (2 credits per second, billed to the account holding the asset), the free-but-lower-priority exploreMode path, and the ~50 s wait window. It also explains the two return outcomes (video url/assetId, failure reason, or a taskId for runway_get_task), which the annotations cannot convey.

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?

Front-loaded with the core action and scope, then cost, then the sibling disambiguation, then the return contract — a sensible order with no filler sentences. It is dense and long for a single description, but every clause carries distinct information (resolution example, billing owner, wait behavior) that the agent would otherwise have to infer.

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?

Although there is no output schema, the description supplies the return contract (url, assetId, failure reason, or taskId plus the follow-up tool) and the async/polling path. For a 6-parameter, open-world mutation tool this covers everything an agent needs to invoke and continue correctly.

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 baseline is 3, but the description adds real meaning: it explains where a valid videoAssetId can come from and ties exploreMode to its credit/priority consequence rather than just restating the flag. The wait parameter's ~50 s behavior is also reinforced in prose alongside the schema text.

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 ('Upscale any video asset ... to 4K with Topaz'), gives the concrete scope limit (up to 40 s, aspect ratio preserved with a worked resolution example), and explicitly distinguishes itself from the sibling runway_upscale_gen4 by naming that sibling's narrower input set.

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?

Names the alternative (runway_upscale_gen4) and the exact condition that selects it ('Gen-4 and Gen-3 Alpha (Turbo) videos only'), while declaring this tool's accepted inputs — a video from runway_create_video or any other Runway task, plus your own uploads. The exploreMode/credits trade-off is also framed as a decision the agent can make.

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