Skip to main content
Glama

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

List Runway accounts

runway_list_accounts
Read-onlyIdempotent

The Runway accounts added to this useapi.net API token, as stored: email, maxJobs (tasks at once), the paid workspace it bills against when set (id, name, plan), session issue and expiry times, and any stored account error; passwords and session tokens are never returned. email reads one account. No call to Runway: runway_get_features shows live credits and plan. Accounts are added on the setup page, not here. GET /accounts.

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

Input Schema

NameRequiredDescriptionDefault
emailNoOne account's email; omit to list them all.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, it discloses that the data is 'as stored', that no Runway call is made, and that passwords and session tokens are never returned, which reassures on sensitivity. It does not say what happens when an email matches nothing or how results are ordered, leaving a small gap for an open-world read tool.

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 returned payload, then the filter, the alternative, and the setup caveat — each sentence carries distinct information with no filler. The telegraphic fragments ('No call to Runway:', 'GET /accounts.') read tersely but remain parseable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description properly compensates by enumerating returned fields and exclusions, and it clarifies the tool's relationship to the mutation path (accounts are added elsewhere). Missing only minor operational detail such as unknown-email behavior or result ordering.

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 single parameter is fully described there ('One account's email; omit to list them all'), so the baseline is 3. The description's 'email reads one account' restates the schema rather than adding new meaning such as case-sensitivity or partial-match behavior.

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 the exact resource (the accounts registered to this useapi.net API token) and enumerates the fields returned (email, maxJobs, workspace id/name/plan, session issue/expiry, stored error). It explicitly contrasts itself with runway_get_features ('shows live credits and plan'), so an agent can separate stored-account metadata from live Runway data 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?

It states the single-account mode ('email reads one account'), the alternative for live credit/plan data ('runway_get_features'), and a clear when-not ('Accounts are added on the setup page, not here'). The agent knows both when to call this and when to route elsewhere.

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