Skip to main content
Glama

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

Upscale a Gen-4 video to 4K

runway_upscale_gen4

Upscale a Gen-4, Gen-4 Turbo, Gen-3 Alpha or Gen-3 Alpha Turbo video asset to 4K with Runway's own upscaler. For any other video (Kling, Veo, Seedance, Wan and the rest, or your own upload) use runway_upscale_video (Topaz). Waits up to ~50 s, then returns the video url and assetId, the failure reason or the taskId for runway_get_task. Uses credits, or none with exploreMode. POST /gen4/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": {
      "assetId": "<assetId>"
    },
    "name": "runway_upscale_gen4"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the task to finish (default true); false returns the taskId at once.
assetIdYesassetId, the Gen-4, Gen-4 Turbo, Gen-3 Alpha or Gen-3 Alpha Turbo video to upscale: 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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations (which only declare non-read-only, open-world, non-idempotent, non-destructive), the description discloses the ~50 s wait budget, the possible return shapes (video url and assetId, failure reason, or taskId), credit consumption with the exploreMode exemption, and that the task bills to the account holding the asset. It does not cover retry/idempotency implications of re-upscaling the same asset, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the capability, then the routing rule, then outcomes and cost. Every clause carries information an agent needs; nothing is padded.

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?

With no output schema, the description still enumerates the possible return values and the follow-up tool, and it covers the cost and account-ownership implications of a non-destructive but credit-consuming mutation. Nothing material is missing for correct invocation.

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 cross-parameter meaning: it ties the wait flag to which return value the agent gets and pairs exploreMode with credit spend versus lower priority. The assetId provenance list largely restates the schema, so it is not a full 5.

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 opens with a specific verb and resource ('Upscale a Gen-4, Gen-4 Turbo, Gen-3 Alpha or Gen-3 Alpha Turbo video asset to 4K') and names the exact model family it accepts, which immediately separates it from runway_upscale_video. The agent can pick correctly 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?

It states both sides of the routing decision explicitly: this tool for Runway Gen-3/Gen-4 assets, and runway_upscale_video (Topaz) for Kling, Veo, Seedance, Wan or user uploads. It also tells the agent to hand a returned taskId to runway_get_task, so the follow-up path is covered too.

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