Skip to main content
Glama

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

Get credits and plan

runway_get_features
Read-onlyIdempotent

Ask Runway live for one account's plan credits (permitted.numPlanCredits) and how many are used (used.numPlanCredits), its storage allowance (permitted.storageGB) and the workspaces (teams) it belongs to with their currentPlan (not null = a paid workspace) and planExpiration; the rest of Runway's answer is passed through as is. Use before a generation to check credits; runway_list_accounts shows the stored settings without calling Runway. GET /features.

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

Input Schema

NameRequiredDescriptionDefault
emailNoThe Runway account email to check (runway_list_accounts). Required when you have several Runway accounts; with one it may be left out.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real context beyond that: this makes a live network call to GET /features, the remaining response is passed through unchanged, and 'currentPlan not null = a paid workspace' explains a field's semantics. It does not discuss rate limits or error behavior when Runway is unreachable, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and the description is dense rather than padded. However, the single semicolon-joined run-on carrying several dotted field paths is somewhat hard to scan, so it loses a point on structure rather than length.

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?

There is no output schema, so the description must describe the return values itself, and it does so by naming the credits, used credits, storage allowance, workspaces, currentPlan and planExpiration fields plus the passthrough behavior. Combined with a fully documented one-parameter schema and complete annotations, nothing material 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 single email parameter is fully documented there, including its link to runway_list_accounts, so the schema carries the burden. The description only implies account selection via 'one account's plan credits' and adds no format or edge-case detail about the email itself, making the baseline 3 appropriate.

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 gives a specific verb and resource ('Ask Runway live for one account's plan credits... and storage allowance') and enumerates the concrete fields returned with their dotted paths, so an agent knows exactly what it gets. It also explicitly separates itself from runway_list_accounts, which returns stored settings instead of a live call.

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 trigger directly ('Use before a generation to check credits') and names the alternative with the distinguishing condition ('runway_list_accounts shows the stored settings without calling Runway'). The live-vs-cached distinction is exactly the decision an agent needs to make between the two.

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