Skip to main content
Glama

list-executions

Retrieve and filter all executions from your N8N MCP instance using parameters like workflow ID, status, and data inclusion to manage and analyze workflow processes effectively.

Instructions

Retrieve all executions from your instance with optional filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientIdYes
includeDataNo
limitNo
statusNo
workflowIdNo

Implementation Reference

  • Executes the list-executions tool by retrieving the N8nClient instance and calling its getExecutions method with provided filters.
    case "list-executions": {
      const { clientId, includeData, status, workflowId, limit } = args as {
        clientId: string;
        includeData?: boolean;
        status?: 'error' | 'success' | 'waiting';
        workflowId?: string;
        limit?: number;
      };
      const client = clients.get(clientId);
      if (!client) {
        return {
          content: [{
            type: "text",
            text: "Client not initialized. Please run init-n8n first.",
          }],
          isError: true
        };
      }
    
      try {
        const executions = await client.getExecutions({ includeData, status, workflowId, limit });
        return {
          content: [{
            type: "text",
            text: JSON.stringify(executions.data, null, 2),
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: error instanceof Error ? error.message : "Unknown error occurred",
          }],
          isError: true
        };
      }
    }
  • Input schema and registration for the list-executions tool in the ListTools response.
    {
      name: "list-executions",
      description: "Retrieve all executions from your instance with optional filtering.",
      inputSchema: {
        type: "object",
        properties: {
          clientId: { type: "string" },
          includeData: { type: "boolean" },
          status: { 
            type: "string",
            enum: ["error", "success", "waiting"]
          },
          workflowId: { type: "string" },
          limit: { type: "number" }
        },
        required: ["clientId"]
      }
    },
  • N8nClient.getExecutions method implements the API call to /executions endpoint with query parameters for filtering executions.
    async getExecutions(options: { 
      includeData?: boolean; 
      status?: 'error' | 'success' | 'waiting';
      workflowId?: string;
      limit?: number;
    } = {}): Promise<N8nExecutionList> {
      const params = new URLSearchParams();
      if (options.includeData !== undefined) params.append('includeData', String(options.includeData));
      if (options.status) params.append('status', options.status);
      if (options.workflowId) params.append('workflowId', options.workflowId);
      if (options.limit) params.append('limit', String(options.limit));
    
      return this.makeRequest<N8nExecutionList>(`/executions?${params.toString()}`);
    }
  • Type definition for the response from n8n executions list API.
    interface N8nExecutionList {
      data: N8nExecution[];
      nextCursor?: string;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'retrieves' executions without disclosing behavioral traits like pagination, rate limits, permissions needed, or what 'includeData' entails. It lacks details on response format or any side effects, leaving significant gaps for a tool with 5 parameters.

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 sentence with no wasted words, front-loading the core action and key feature (filtering). Every part earns its place, making it highly concise and well-structured.

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

Completeness2/5

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

Given the tool's complexity (5 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain return values, error handling, or parameter interactions, leaving too much undefined for effective agent use despite the concise structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but only vaguely mentions 'optional filtering' without explaining parameters like 'clientId', 'includeData', 'limit', 'status', or 'workflowId'. It adds minimal meaning beyond the schema, failing to clarify parameter purposes or usage.

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 clearly states the verb 'retrieve' and resource 'executions' with scope 'from your instance', making the purpose understandable. It distinguishes from siblings like 'get-execution' by specifying 'all executions' with filtering, though it doesn't explicitly contrast with other list tools like 'list-projects'.

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 mentions 'optional filtering' but provides no guidance on when to use this tool versus alternatives like 'get-execution' for single executions or other list tools. There are no explicit when/when-not instructions or prerequisites stated.

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

Related 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/fellipesaraiva88/n8n-mcp-server'

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