Skip to main content
Glama

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

Delete an asset

runway_delete_asset
DestructiveIdempotent

Delete one asset (an uploaded or generated file) from its Runway account by assetId; the account comes from the assetId. To remove a generation from the task history use runway_delete_task instead. Answers success: true; an unknown assetId answers 404. Cannot be undone. DELETE /assets/{assetId}.

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": {
      "assetId": "<assetId>"
    },
    "name": "runway_delete_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesThe assetId to delete, e.g. user:12345-runwayml:name@example.com-asset:<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, but the description adds genuinely new behavior: irreversibility ("Cannot be undone"), a 404 for unknown assetId, and a success:true response. It stops short of describing partial-failure or permission behavior, keeping it just under full marks.

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 tight clauses plus a terminal endpoint, front-loaded with the action and scope, then the sibling exclusion, then behavioral facts. No filler sentences and nothing repeated.

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 one-parameter destructive tool with no output schema, the definition covers routing, irreversibility, and both success and 404 outcomes. An agent has everything needed to call it correctly and to warn about consequences.

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 coverage is 100% and the schema entry already explains the assetId format and that it encodes the account, so the description's note largely restates it. It confirms the single-parameter design but adds no new naming or format detail beyond 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 ("Delete one asset ... by assetId") plus scope (uploaded or generated file in a Runway account). It explicitly contrasts with the similarly named sibling runway_delete_task, so an agent can route correctly without opening a 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 an explicit negative case: to remove a generation from task history, use runway_delete_task instead. It also preempts the obvious question of why no account parameter exists by noting the account is derived from the assetId.

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