Skip to main content
Glama

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

List tasks

runway_list_tasks
Read-onlyIdempotent

List one Runway account's task history, generations started in the Runway web app included: taskId, taskType, name (first 200 characters), status (PENDING, RUNNING, THROTTLED, SUCCEEDED, FAILED), createdAt, progressRatio, error and the finished files in artifacts (assetId, url, filename); runway_get_task gives a task's full record with its options. Page with offset and limit (1-1000, default 10); statuses filters, e.g. PENDING, RUNNING and THROTTLED for everything still running. runway_list_running_tasks shows only what this API is tracking now; runway_get_task reads one task. GET /tasks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "runway_list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe Runway account email to list (runway_list_accounts). Required when you have several Runway accounts; with one it may be left out.
limitNoTasks to return, 1-1000 (default 10).
offsetNoPaging offset, 0 for the first page (default 0).
statusesNoOnly tasks with one of these statuses. Default: all.

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?

The annotations already establish that this is a safe read-only operation, and the description adds substantial context beyond them: task history includes web-app generations, return fields are enumerated, pagination defaults are stated, and status filtering behavior is explained. This is exactly the behavioral detail an agent needs when selecting and interpreting the call.

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

Conciseness3/5

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

The description is front-loaded and generally efficient for a tool whose output fields are important because there is no output schema. However, it is a dense semicolon-heavy paragraph that repeats the runway_get_task comparison twice, which is avoidable duplication.

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?

Because there is no output schema, the enumeration of returned fields such as taskId, status, progressRatio, error, and artifacts is valuable and largely complete. The main remaining gap is that it does not state the ordering or retention window of the task history, which would help an agent interpret paginated results.

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 defines all four parameters, establishing a baseline of 3. The description adds practical meaning by explaining the statuses filter use case with PENDING, RUNNING, and THROTTLED for everything still running, and by restating the limit range and default.

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 states a specific verb and resource: list one Runway account's task history. It also names the included scope (generations started in the web app) and distinguishes the tool from runway_get_task and runway_list_running_tasks, so an agent can identify it without opening the 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 explicitly routes the agent to runway_get_task for a task's full record and to runway_list_running_tasks for only what the API is currently tracking. It also explains how to use statuses for still-running tasks, giving a concrete when-to-use pattern.

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