Skip to main content
Glama

List Workflow Runs

workflow_runs
Read-onlyIdempotent

Run history for one workflow, newest first, with per-step outcomes. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesworkflowId returned by workflows_list or a workflow write.
limitNoMaximum recent runs; default 10. The API caps at 50 even when a larger value is supplied.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
runsYesRun history for the requested workflow, newest first. Empty means no runs are recorded. Queued or running is unfinished; inspect error and stepResults on failed or abandoned runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / runs / items / properties / found / properties / contacts / description
      Previous value: -"People first saved by this run."New value: +"Contacts first saved by this run."
    • addedOutput schema / properties / runs / items / properties / found / properties / people
      Added value: +{
      +  "description": "People this run added to a company's research list but not as contacts.",
      +  "type": "number"
      +}
  2. Changed17 schema fields changed
    • changedOutput schema / properties / runs / description
      Previous value: -"Newest runs first."New value: +"Run history for the requested workflow, newest first. Empty means no runs are recorded. Queued or running is unfinished; inspect error and stepResults on failed or abandoned runs."
    • addedOutput schema / properties / runs / items / properties / error / description
      Added value: +"Reported failure or abandonment reason, or null when none is recorded."
    • changedOutput schema / properties / runs / items / properties / finishedAt / description
      Previous value: -"Unix epoch milliseconds."New value: +"Completion time as Unix epoch milliseconds, or null while unfinished."
    • addedOutput schema / properties / runs / items / properties / found / description
      Added value: +"New records attributed to this run. Use its id in leads_list.workflowRunId to inspect them."
    • addedOutput schema / properties / runs / items / properties / found / properties / contacts / description
      Added value: +"People first saved by this run."
    • addedOutput schema / properties / runs / items / properties / found / properties / leads / description
      Added value: +"Companies first saved by this run."
    • addedOutput schema / properties / runs / items / properties / headline / description
      Added value: +"Agent's summary of the run, or null before one is reported."
    • changedOutput schema / properties / runs / items / properties / startedAt / description
      Previous value: -"Unix epoch milliseconds."New value: +"Run start or queue time as Unix epoch milliseconds."
    • changedOutput schema / properties / runs / items / properties / stepResults / description
      Previous value: -"Per-step outcomes and linked review cards."New value: +"Reported steps with their latest outcomes, notes and review-card links; empty before any step reports."
    • addedOutput schema / properties / runs / items / properties / stepResults / items / properties / at
      Added value: +{
      +  "description": "When this step reported, as Unix epoch milliseconds.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / runs / items / properties / stepResults / items / properties / gateUnmet
      Added value: +{
      +  "description": "True when a required approval step reported without a valid approval card as evidence.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / runs / items / properties / stepResults / items / properties / note
      Added value: +{
      +  "description": "Additional explanation, or null when omitted.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / runs / items / properties / stepResults / items / properties / outcome
      Added value: +{
      +  "description": "Agent-reported outcome text; this is not a fixed status enum.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / runs / items / properties / stepResults / items / properties / reviewItemId
      Added value: +{
      +  "description": "Linked review card ID for review_get, or null when none was created.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / runs / items / properties / stepResults / items / properties / stepId
      Added value: +{
      +  "description": "ID of the workflow step that reported this outcome.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / runs / items / properties / stepResults / items / required
      Added value: +[
      +  "stepId",
      +  "outcome",
      +  "note",
      +  "at",
      +  "reviewItemId",
      +  "gateUnmet"
      +]
    • addedOutput schema / properties / runs / items / properties / workflowVersion
      Added value: +{
      +  "description": "Workflow revision captured for this run; it may differ from the current workflow version.",
      +  "type": "number"
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"workflowId returned by workflows_list or a workflow write."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum recent runs; default 10. The API caps at 50 even when a larger value is supplied."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "runs": {
      +      "description": "Newest runs first.",
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "error": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "finishedAt": {
      +            "description": "Unix epoch milliseconds.",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "found": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "contacts": {
      +                "type": "number"
      +              },
      +              "leads": {
      +                "type": "number"
      +              }
      +            },
      +            "required": [
      +              "leads",
      +              "contacts"
      +            ],
      +            "type": "object"
      +          },
      +          "headline": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "description": "Run ID for leads_list.workflowRunId.",
      +            "type": "string"
      +          },
      +          "startedAt": {
      +            "description": "Unix epoch milliseconds.",
      +            "type": "number"
      +          },
      +          "status": {
      +            "description": "Run state, such as queued, running, done, failed or abandoned.",
      +            "type": "string"
      +          },
      +          "stepResults": {
      +            "description": "Per-step outcomes and linked review cards.",
      +            "items": {
      +              "additionalProperties": true,
      +              "properties": {},
      +              "type": "object"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "status"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "runs"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only' adds nothing. The description does add real behavioral context beyond the annotations: results are ordered newest first and include per-step outcomes. It says nothing about pagination or how to reach runs beyond the limit window.

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?

Very short and front-loaded: scope, ordering, and return shape come first. The trailing 'Read-only.' is pure duplication of readOnlyHint=true and does not earn its place, which keeps this from a 5.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. Scope, ordering, and content shape are covered; the only real gap is how an agent retrieves runs older than the limit window, which the capped limit parameter hints at but the description never addresses.

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%, so both parameters are fully documented in the schema, including the default and the API's 50-run cap. The description adds no parameter-level meaning beyond 'one workflow', which the schema already conveys. Baseline 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?

States a specific verb (list run history) and resource (one workflow), plus the ordering and the per-step outcome content. It does not explicitly distinguish itself from siblings like workflows_list or results_get, but the resource is narrow enough that confusion is unlikely.

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

Usage Guidelines3/5

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

Usage is only implied: 'for one workflow' suggests you need a workflowId, but there is no when-to-use vs. workflows_list, no statement of when run history is the right call versus results_get, and no exclusions. Adequate but leaves routing to inference.

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