Skip to main content
Glama

list_executions

View and filter workflow execution history by status, workflow ID, or limit results to monitor automation performance and troubleshoot issues.

Instructions

List workflow executions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdNoFilter by workflow ID
statusNoFilter by execution status
limitNoLimit number of results

Implementation Reference

  • Handler logic for the 'list_executions' tool in the CallToolRequestSchema switch statement. It calls main.api.listExecutions(args) and returns the result as JSON text content.
    case "list_executions":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.listExecutions(args), null, 2)
          }
        ]
      };
  • Input schema definition for the 'list_executions' tool, defining optional parameters for filtering executions.
    inputSchema: {
      type: "object",
      properties: {
        workflowId: {
          type: "string",
          description: "Filter by workflow ID"
        },
        status: {
          type: "string",
          enum: ["success", "failure", "running"],
          description: "Filter by execution status"
        },
        limit: {
          type: "number",
          description: "Limit number of results"
        }
      }
    }
  • Registration of the 'list_executions' tool in the tools list returned by ListToolsRequestSchema handler.
    {
      name: "list_executions",
      description: "List workflow executions",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "Filter by workflow ID"
          },
          status: {
            type: "string",
            enum: ["success", "failure", "running"],
            description: "Filter by execution status"
          },
          limit: {
            type: "number",
            description: "Limit number of results"
          }
        }
      }
    },
  • Helper function listExecutions in apiHelpers, which is called by the tool handler. Currently a stub awaiting implementation.
    listExecutions: async function(args: any = {}) {
      // ... copy listExecutions logic from index.ts ...
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List workflow executions' implies a read-only operation but doesn't specify whether it returns all executions or requires pagination, what permissions are needed, or the format of returned data. For a tool with 3 parameters and no annotations, this leaves significant behavioral gaps.

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?

The description is a single, efficient phrase that communicates the core purpose without any wasted words. It's perfectly front-loaded and appropriately sized for a simple listing tool.

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?

For a listing tool with good schema coverage but no annotations and no output schema, the description is minimally adequate. It identifies the resource type but doesn't provide context about what 'executions' entail, how results are structured, or important behavioral constraints. The schema handles parameter documentation, but overall context remains incomplete.

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?

The input schema has 100% description coverage, clearly documenting all three parameters with their purposes and constraints. The description doesn't add any parameter information beyond what's in the schema, but since the schema is comprehensive, the baseline score of 3 is appropriate.

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 'List workflow executions' clearly states the verb ('List') and resource ('workflow executions'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'list_workflows' or 'list_connections' by specifying the resource type. However, it doesn't specify scope or filtering capabilities, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when filtering is appropriate, or how it relates to sibling tools like 'get_workflow' or 'list_workflows'. The agent must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/milisp/automatisch-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server