Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

List n8n Executions

n8n_list_executions
Read-onlyIdempotent

Retrieve and filter workflow execution records to monitor automation performance and troubleshoot issues.

Instructions

List workflow executions with optional filtering.

Args:

  • workflowId (string, optional): Filter by workflow ID

  • status (string, optional): Filter by status (error, success, waiting, new, running, canceled, crashed)

  • includeData (boolean): Include full execution data (default: false)

  • projectId (string, optional): Filter by project ID

  • limit (number): Maximum results (default: 100)

  • cursor (string, optional): Pagination cursor

Returns: List of executions with id, workflowId, status, mode, timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdNoFilter by workflow ID
statusNoFilter by execution status
includeDataNoInclude full execution data
projectIdNoFilter by project ID
limitNoMaximum results to return
cursorNoPagination cursor

Implementation Reference

  • Registration and handler implementation for n8n_list_executions tool.
      // ============ List Executions ============
      server.registerTool(
        'n8n_list_executions',
        {
          title: 'List n8n Executions',
          description: `List workflow executions with optional filtering.
    
    Args:
      - workflowId (string, optional): Filter by workflow ID
      - status (string, optional): Filter by status (error, success, waiting, new, running, canceled, crashed)
      - includeData (boolean): Include full execution data (default: false)
      - projectId (string, optional): Filter by project ID
      - limit (number): Maximum results (default: 100)
      - cursor (string, optional): Pagination cursor
    
    Returns:
      List of executions with id, workflowId, status, mode, timestamps.`,
          inputSchema: ListExecutionsSchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
          }
        },
        async (params: z.infer<typeof ListExecutionsSchema>) => {
          const queryParams: Record<string, unknown> = {
            limit: params.limit,
            includeData: params.includeData
          };
          if (params.workflowId) queryParams.workflowId = params.workflowId;
          if (params.status) queryParams.status = params.status;
          if (params.projectId) queryParams.projectId = params.projectId;
          if (params.cursor) queryParams.cursor = params.cursor;
          
          const response = await get<N8nPaginatedResponse<N8nExecutionListItem>>('/executions', queryParams);
          
          const formatted = response.data.map(formatExecution).join('\n\n---\n\n');
          const output = {
            count: response.data.length,
            executions: response.data,
            nextCursor: response.nextCursor
          };
          
          let text = `Found ${response.data.length} execution(s):\n\n${formatted}`;
          if (response.nextCursor) {
            text += `\n\n_More results available. Use cursor: ${response.nextCursor}_`;
          }
          
          return {
            content: [{ type: 'text', text }],
            structuredContent: output
          };
        }
      );
Behavior3/5

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

Annotations already indicate read-only, non-destructive, and idempotent behavior, which the description does not contradict. The description adds context about pagination (via 'cursor') and default values (e.g., 'limit' default: 100), but lacks details on rate limits, authentication needs, or error handling. With annotations covering safety, this earns a baseline 3.

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 well-structured with a clear purpose statement followed by 'Args:' and 'Returns:' sections. It is front-loaded and avoids unnecessary details, though the parameter listing could be more concise. Overall, it is efficient with little waste.

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?

Given the annotations cover safety (read-only, non-destructive) and the schema fully describes parameters, the description is mostly complete. It includes return value details (list of executions with fields) despite no output schema, but lacks context on error cases or performance limits. For a list tool with good annotations, this is sufficient.

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%, meaning all parameters are documented in the schema. The description adds minimal value by listing parameters and their purposes (e.g., 'Filter by workflow ID'), but does not provide additional semantics beyond the schema. This meets the baseline of 3 for high schema coverage.

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 tool's purpose as 'List workflow executions with optional filtering,' which specifies the verb ('List') and resource ('workflow executions'). It distinguishes from siblings like 'n8n_get_execution' (singular) and 'n8n_delete_executions' (deletion), but does not explicitly differentiate from other list tools (e.g., 'n8n_list_workflows'), making it a 4.

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 mentions optional filtering but does not specify when to use it over other list tools (e.g., 'n8n_list_workflows') or when filtering is appropriate, resulting in a minimal score of 2.

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/DrBalls/n8n-mcp-server-v2'

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