Skip to main content
Glama

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

Delete a task

runway_delete_task
DestructiveIdempotent

Delete one task from its Runway account's task history by taskId; the account comes from the taskId. To delete a single file use runway_delete_asset; to stop this API tracking a running task (and free its slot) use runway_cancel_task. Answers success: true; an unknown taskId answers 404. Cannot be undone. DELETE /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_delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesThe taskId to delete, 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.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds value beyond them by disclosing the return shape (success: true), the failure mode (unknown taskId answers 404), and that the action cannot be undone. It does not explicitly say what happens if the task is currently running (that is only implicit via the cancel_task pointer), 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?

Front-loaded with the core action, then sibling disambiguation, then behavioral notes, then the underlying route. Every clause carries unique information with no filler.

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 destructive tool with no output schema, it covers the action, the routing, the success response, and the error case. Nothing an agent needs in order to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the taskId description already explains that the identifier names the account. The description's 'the account comes from the taskId' reinforces that no separate account parameter is needed, but adds only marginal meaning over the 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 and resource with scope: 'Delete one task from its Runway account's task history by taskId'. It also names the two nearest siblings it is not (runway_delete_asset, runway_cancel_task), so an agent can distinguish it without opening any 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?

Gives explicit alternatives with the condition that selects each: single file deletion routes to runway_delete_asset, and stopping tracking of a running task (freeing its slot) routes to runway_cancel_task. This is a textbook when-to-use-this-vs-that routing block.

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