Skip to main content
Glama

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

Describe an image

runway_describe_image
Read-onlyIdempotent

Turn an image asset into a detailed text description (subject, scene, style) to edit and use as a prompt, for example in runway_create_frames or runway_create_image. Free and unlimited on every Runway account, the free plan too; answers at once, no task. Upload the image first with runway_upload_asset. GET /frames/describe/{image_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": {
      "image_assetId": "<image_assetId>"
    },
    "name": "runway_describe_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_assetIdYesimage_assetId, the image to describe: an assetId from runway_upload_asset, runway_list_assets or a finished task (runway_get_task artifacts). The task runs on the Runway account that holds the asset.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: cost profile (free and unlimited, including the free plan), latency/synchronous semantics (answers at once, no task object created), and the underlying endpoint. An agent knows this is a cheap, immediate read with no task polling required — none of which the readOnly/idempotent hints convey.

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?

Two dense sentences that front-load the purpose before prerequisites and cost. The pricing and 'no task' clauses are slightly crammed together, but each carries decision-relevant information an agent would otherwise lack.

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 one required parameter, no output schema, and full annotation coverage, the description supplies everything missing: what the output contains, how to obtain a valid input, that no task is created, and that it is free — sufficient for correct invocation without further inference.

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 parameter's accepted assetId sources plus account-scoping note are already documented in the schema. The description only reinforces the upload prerequisite, adding no new syntax or constraint beyond the structured field.

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 concrete transformation — image asset to text description — and names the facets returned (subject, scene, style), which distinguishes it from sibling generators like runway_create_image and runway_create_frames that consume such descriptions rather than produce them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit prerequisite chain (upload first via runway_upload_asset) and a concrete downstream use case (prompt input for runway_create_frames or runway_create_image). It stops short of stating when not to use it, but no competing sibling performs the same job, so the guidance is effectively complete.

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