Skip to main content
Glama

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

Stop tracking a task

runway_cancel_task
DestructiveIdempotent

Stop this API tracking a running task (a taskId from runway_list_running_tasks) and free its maxJobs slot on the account. It does not cancel the task at Runway: the generation carries on and uses the account's credits, runway_get_task still reads it, but its replyUrl callback is no longer sent. 404 when the taskId is not being tracked. Cannot be undone. DELETE /scheduler/{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_cancel_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesThe taskId to stop tracking, 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?

With destructiveHint and idempotentHint already declared, the description still adds substantial context the annotations cannot convey: the generation continues and consumes credits, runway_get_task still reads it, the replyUrl callback is suppressed, and a 404 is returned for untracked IDs. "Cannot be undone" aligns with destructiveHint rather than contradicting it.

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 dense sentences, front-loaded with the core action, followed by the key side effects and the failure mode, ending with the HTTP verb and path. No sentence is redundant and nothing is buried.

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 single-parameter mutation with no output schema, the description covers the action, its external side effects, billing implications, the callback consequence, the 404 case, and irreversibility. An agent has everything needed to decide and invoke 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% and the schema already gives an example format, so the baseline applies. The description adds real meaning by stating the ID comes from runway_list_running_tasks and that the ID encodes the account, which helps an agent source a valid value rather than just format one.

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 uses a specific verb+resource ("stop this API tracking a running task") and immediately disambiguates the most tempting misreading: "It does not cancel the task at Runway." That contrast separates it from cancellation/deletion siblings without needing their schemas.

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?

It tells the agent where the taskId comes from (runway_list_running_tasks) and what effect stopping tracking has versus leaving the task running, which is a clear usage context. It stops short of explicitly naming an alternative tool to use when the goal is actually to cancel, leaving that inference to the reader.

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