Skip to main content
Glama

n8n_list_executions

Retrieve workflow execution history with filters for workflow ID, status, and data inclusion to monitor and analyze automation performance.

Instructions

List workflow executions. Can filter by workflow ID and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdNoFilter executions by workflow ID
statusNoFilter by execution status
limitNoMaximum number of executions to return (default: 20)
includeDataNoInclude execution data in response (default: false)

Implementation Reference

  • The async handler function implementing the core logic of n8n_list_executions. It calls N8nApiClient.listExecutions with filtered parameters, maps execution data, and returns formatted JSON response with count, executions list, and pagination info.
    n8n_list_executions: async (
      client: N8nApiClient,
      args: Record<string, unknown>
    ): Promise<ToolResult> => {
      const result = await client.listExecutions({
        workflowId: args.workflowId as string | undefined,
        status: args.status as 'success' | 'error' | 'waiting' | undefined,
        limit: (args.limit as number) || 20,
        includeData: args.includeData as boolean | undefined,
      });
    
      const executions = result.data.map((e) => ({
        id: e.id,
        workflowId: e.workflowId,
        status: e.status,
        mode: e.mode,
        startedAt: e.startedAt,
        stoppedAt: e.stoppedAt,
        finished: e.finished,
      }));
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify({
              count: executions.length,
              executions,
              hasMore: !!result.nextCursor,
            }, null, 2),
          },
        ],
      };
    },
  • ToolDefinition object specifying the name, description, and inputSchema for validating parameters: workflowId (string), status (enum), limit (number), includeData (boolean).
    {
      name: 'n8n_list_executions',
      description: 'List workflow executions. Can filter by workflow ID and status.',
      inputSchema: {
        type: 'object',
        properties: {
          workflowId: {
            type: 'string',
            description: 'Filter executions by workflow ID',
          },
          status: {
            type: 'string',
            enum: ['success', 'error', 'waiting'],
            description: 'Filter by execution status',
          },
          limit: {
            type: 'number',
            description: 'Maximum number of executions to return (default: 20)',
          },
          includeData: {
            type: 'boolean',
            description: 'Include execution data in response (default: false)',
          },
        },
      },
    },
  • src/server.ts:127-131 (registration)
    Dispatch/registration logic in the main server handleToolCall method that routes calls to executionToolHandlers if the tool name matches, invoking the handler with API client and arguments.
    // Execution tools
    if (name in executionToolHandlers) {
      const handler = executionToolHandlers[name as keyof typeof executionToolHandlers];
      return handler(client, args);
    }
  • Aggregation of all tool definitions including executionTools (containing n8n_list_executions schema), exported as allTools for MCP server tool listing.
    export const allTools: ToolDefinition[] = [
      ...documentationTools,  // Documentation first for discoverability
      ...workflowTools,
      ...executionTools,
    ];
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. It mentions filtering capabilities but fails to describe critical behaviors: whether this is a read-only operation, if it supports pagination beyond the 'limit' parameter, what the response format looks like, or any rate limits. For a list tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a list tool and front-loads the core purpose. While it could be slightly more comprehensive, every word earns its place by conveying essential information about the tool's function.

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 complexity of a list operation with 4 parameters and no output schema, the description is incomplete. It doesn't explain what the tool returns (execution objects with what fields?), whether results are paginated, or any behavioral constraints. With no annotations and no output schema, the description should provide more context about the operation's results and limitations to be truly helpful.

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 schema description coverage is 100%, so the schema already fully documents all 4 parameters. The description mentions filtering by workflow ID and status, which aligns with two parameters but adds no additional meaning beyond what the schema provides. With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't detract either.

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 ('List') and resource ('workflow executions'), making the purpose immediately understandable. It distinguishes from siblings like 'n8n_get_execution' (singular) and 'n8n_delete_execution' (destructive), though it doesn't explicitly mention these distinctions. The mention of filtering adds specificity but doesn't fully differentiate from all siblings.

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 siblings like 'n8n_get_execution' for single executions or 'n8n_list_workflows' for listing workflows instead of executions. There's no context about prerequisites, typical use cases, or exclusions, leaving the agent to 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/alicankiraz1/cursor-n8n-builder'

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