Skip to main content
Glama

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

Get an asset

runway_get_asset
Read-onlyIdempotent

One asset by assetId (from runway_upload_asset, runway_list_assets or a task's artifacts): name, mediaType, url, previewUrls, fileSize, media metadata (duration, width, height) and the taskId of a generated file. An unknown or deleted assetId answers 404. runway_list_assets lists many; runway_get_task reads a generation with its status. GET /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_get_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesThe assetId to read, 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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds two things annotations cannot: the 404 behavior for an unknown or deleted assetId, and the full set of returned fields in the absence of an output schema. It stops short of any auth or pagination/rate-limit context, so it is strong but not exhaustive.

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?

The core operation and its return shape are front-loaded in the first sentence, followed by the error case, then the sibling disambiguation, then the endpoint. No sentence is filler, and the density is justified because no output schema exists to carry the return-field list.

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 read tool with no output schema, the description covers everything an agent needs: how to obtain the id, what comes back, what failure looks like, and when to prefer siblings. Nothing material is left to inference.

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 baseline is 3, and the schema already explains the account-qualified assetId format. The description still adds meaning beyond it by stating where valid assetIds originate (upload, list, or a task's artifacts), which reduces the chance of a fabricated id.

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 ('One asset by assetId') and enumerates exactly what is returned (name, mediaType, url, previewUrls, fileSize, media metadata, taskId). It explicitly contrasts with runway_list_assets ('lists many') and runway_get_task ('reads a generation with its status'), so an agent can select it without opening another 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 the input's provenance explicitly ('from runway_upload_asset, runway_list_assets or a task's artifacts'), which tells the agent when this tool is the right follow-up call. It also names the alternatives and the condition that separates them, plus the underlying endpoint for operators.

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