Skip to main content
Glama

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

List running tasks

runway_list_running_tasks
Read-onlyIdempotent

The tasks this API is tracking now (started through it and not yet finished), each with its taskId and the replyUrl / replyRef given at create. The first check when a create tool answers 429: each account runs at most its maxJobs tasks at once (runway_list_accounts). Tasks started in the Runway web app are not here: use runway_list_tasks with statuses PENDING, RUNNING, THROTTLED. GET /scheduler.

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_running_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real context beyond them: the tracking scope excludes web-app tasks, and each returned item carries taskId plus replyUrl/replyRef. It stops short of explaining pagination, ordering, or how replyUrl/replyRef should be used, keeping it just below the top mark.

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 what is returned, then the 429 diagnostic, then the exclusion rule — a sensible order with no filler. The phrasing is dense to the point of being terse, and 'The tasks this API is tracking now' plus the parenthetical takes a second read to parse.

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?

For a zero-parameter read-only list with no output schema, the description supplies the scope, the shape of each returned item (taskId, replyUrl/replyRef), and the failure mode it diagnoses. Nothing needed to invoke it correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter space the description could further illuminate. The use of 'statuses PENDING, RUNNING, THROTTLED' applies to a sibling tool rather than this one's schema.

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+resource ('the tasks this API is tracking now') with an explicit scope definition — tasks started through the API and not yet finished. Parenthetical disambiguation from tasks visible in the Runway web app makes it clearly separable from runway_list_tasks.

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?

Gives an explicit trigger ('the first check when a create tool answers 429'), explains the underlying constraint (each account runs at most its maxJobs tasks at once), and routes to the named alternatives: runway_list_accounts for limits and runway_list_tasks with statuses PENDING/RUNNING/THROTTLED for web-app-originated work.

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