Skip to main content
Glama

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

List assets

runway_list_assets
Read-onlyIdempotent

List one Runway account's assets, uploads and generated files alike (web app included): assetId, name, mediaType, url, previewUrls, fileSize, media metadata (duration, width, height) and, for a generated file, the taskId that made it. Page with offset and limit (1-50, default 20); mediaType filters to video, image or audio. The list is scoped to the account's workspace while runway_get_asset reads by id unscoped, so a readable asset may be missing from the list. runway_get_asset reads one asset; runway_list_tasks lists the generations. GET /assets.

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

Input Schema

NameRequiredDescriptionDefault
emailNoThe Runway account email to list (runway_list_accounts). Required when you have several Runway accounts; with one it may be left out.
limitNoAssets to return, 1-50 (default 20).
offsetNoPaging offset, 0 for the first page (default 0).
mediaTypeNoOnly assets of this media type.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds real behavioral context beyond that: workspace scoping versus the unscoped by-id read, and pagination bounds. It stops short of describing response shape details such as ordering, but the added scoping caveat is substantive.

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 the verb, resource and scope, then the field inventory, then paging and alternatives. The return-field enumeration is dense but earns its place given there is no output schema; only minor tightening is possible.

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?

With no output schema, the field inventory compensates well, and paging, filtering, scoping and sibling routing are all covered. Nothing essential for correct invocation 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 coverage is 100%, so offset, limit, mediaType and email are already documented in the schema, and the description largely restates limit bounds and the media filter. It adds no new meaning for the email parameter, which is the one with non-obvious semantics.

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 names a specific verb and resource ("List one Runway account's assets"), distinguishes uploads from generated files, and enumerates the returned fields. It clearly differentiates itself from runway_get_asset and runway_list_tasks, so an agent can select it without opening the 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?

Explicitly routes to alternatives: "runway_get_asset reads one asset; runway_list_tasks lists the generations." It also explains a non-obvious exclusion — the list is workspace-scoped while get_asset is unscoped, so a readable asset may be absent — which is the exact condition an agent needs to decide which tool to trust.

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