Skip to main content
Glama

list_executions

Read-only

List recent executions of a workflow (newest first): execution_id, status, trigger_source, timing, nodes_executed, error. Filter by status and/or trigger_source (manual|webhook|cron|mcp|api, or an agent's turn: agent_message|agent_text|agent_event|agent_schedule|agent_wakeup|agent_test), or search the error text. Use to find triggered/scheduled/failed runs and their execution_ids.

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>"
    },
    "name": "list_executions"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
beforeNo
searchNo
statusNo
workflow_idYes
trigger_sourceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / trigger_source / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "enum": [
      -        "manual",
      -        "webhook",
      -        "cron",
      -        "mcp",
      -        "api",
      -        "email",
      -        "agent_turn"
      -      ],
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "enum": [
      +        "manual",
      +        "webhook",
      +        "cron",
      +        "mcp",
      +        "api",
      +        "email",
      +        "agent_turn",
      +        "agent_message",
      +        "agent_text",
      +        "agent_event",
      +        "agent_schedule",
      +        "agent_wakeup",
      +        "agent_test"
      +      ],
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuine behavior beyond that: result ordering (newest first), the exact field set returned, and the fact that filters combine (status and/or trigger_source, or error-text search). Pagination behavior for before/after is not disclosed, which is the remaining gap.

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 purpose and return fields, then filtering detail, then usage — good ordering with no filler sentences. The long parenthetical enum list makes the middle sentence dense, but every clause carries information.

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

Completeness3/5

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

The output schema means return values needn't be spelled out, and filters are covered reasonably well. However, for a 7-parameter read tool with zero schema description coverage, three pagination parameters are left unexplained and the trigger_source enumeration is inconsistent with the schema, leaving real gaps in what an agent needs to call it 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?

With 0% schema description coverage the description must carry all parameter meaning, and it only partially does: it explains status, trigger_source values, and that search targets error text, but never explains after, before, or limit (cursor vs. timestamp, page size semantics). It also omits 'email' and 'agent_turn' from the trigger_source list that the schema actually allows, so an agent relying on the prose could mis-filter.

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 and resource — 'List recent executions of a workflow (newest first)' — and enumerates the fields returned, so the agent knows exactly what it gets back. It does not explicitly distinguish itself from execution-detail siblings like get_execution_status or list_checkpoints, which keeps it short of 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?

'Use to find triggered/scheduled/failed runs and their execution_ids' gives a clear selection context, implying this is the discovery entry point before fetching details elsewhere. It stops short of naming an alternative tool or stating when not to use it.

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.