Skip to main content
Glama

Get run outputs

get_run_outputs
Read-only

List the audio a run produced, one entry per output node.

Call once get_run_status reports completed. Nothing is played here — ask the user before you play anything. Each line carries takes[] (one audio_url each), normalized, and delivery_passed. The URLs are short-lived — re-call this tool rather than caching them.

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": {
      "workflow_id": "<workflow_id>",
      "run_id": "<run_id>"
    },
    "name": "get_run_outputs"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run_id from run_workflow or list_runs.
workflow_idYesThe workflow_id from list_workflows. Never invent one.

Output Schema

NameRequiredDescriptionDefault
run_idNo
creditsNo
outputsNo
next_stepNo
run_statusNo
run_console_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / $defs / OutputLineRow / properties / unverified
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/UnverifiedRow"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / $defs / UnverifiedRow
      Added value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "count": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "words": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses that URLs are short-lived and must not be cached, that nothing is played as a side effect, and which fields each line carries (takes[], normalized, delivery_passed). These are non-obvious operational traits an agent could not infer from annotations alone.

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?

Four short sentences, front-loaded with what the tool returns, then the timing rule, then the no-playback warning, then the caching constraint. No sentence is redundant and each carries distinct information.

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 an output schema present, the description need not detail return values, yet it still summarizes the per-entry fields. Combined with the sequencing precondition and URL-expiry warning, an agent has everything needed to select and invoke this correctly.

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 both required parameters already carry provenance hints in the schema. The description adds no additional meaning about workflow_id or run_id, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 (list the audio a run produced) and adds the granularity ('one entry per output node'), which tells an agent exactly what shape the result takes. It does not differentiate from the closely related sibling download_run, which is the main gap keeping this from a 5.

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?

It explicitly states the precondition and sequencing: 'Call once get_run_status reports completed,' which is the key when-to-use rule. It also sets a clear negative constraint ('ask the user before you play anything'). It does not mention download_run as the alternative when the agent actually needs the file rather than the listing.

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.