Skip to main content
Glama

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

Get a task

runway_get_task
Read-onlyIdempotent

One generation by taskId (from any runway_create_* tool or runway_list_tasks): status (PENDING, RUNNING, THROTTLED, SUCCEEDED, FAILED), progressRatio, options, the error of a failed task, and once SUCCEEDED the files in artifacts (url, assetId). wait: true waits up to ~50 s for an unfinished task; call again until it is SUCCEEDED or FAILED. An unknown or deleted taskId answers 404. GET /tasks/{taskId}.

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

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the task to finish (default false: one read).
taskIdYesThe taskId to read, e.g. user:12345-runwayml:name@example.com-task:<uuid> (it names the account).

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?

Annotations only declare it a safe, idempotent, open-world read. The description adds substantial context beyond that: the full status enum, that artifacts appear only once SUCCEEDED, the per-file fields (url, assetId), the ~50 s wait ceiling with a re-call loop, and that an unknown or deleted taskId returns 404.

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?

Tightly packed but front-loaded: the resource and scope lead, the return shape follows, and the polling and error behavior close. No sentence is filler, and even the trailing 'GET /tasks/{taskId}' adds endpoint grounding for a technical agent.

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 takes on the burden of describing returns and does so thoroughly — status values, progressRatio, error, artifacts. Combined with polling behavior and 404 semantics, an agent can call and interpret this tool without further discovery.

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 schema already carries both parameters. The description still adds value by explaining where taskId originates (create tools or list_tasks) and by framing wait as a polling primitive rather than a one-shot flag, though it repeats the schema's ~50 s figure.

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: 'One generation by taskId'. It immediately distinguishes itself from runway_list_tasks by naming the taskId source, and it lists the exact payload fields (status, progressRatio, options, error, artifacts), so an agent knows this is a single-task read, not a listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete operational guidance: taskId comes from any runway_create_* tool or runway_list_tasks, wait:true blocks up to ~50 s, and the agent should call again until SUCCEEDED or FAILED. It does not explicitly exclude alternatives (e.g. runway_list_running_tasks for bulk polling), so it falls just short of a 5.

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