Skip to main content
Glama

n8n_list_executions

Retrieve and filter workflow execution history in n8n to monitor performance, track status, and analyze results using pagination and status-based queries.

Instructions

List workflow executions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of executions to return (default: 20)
cursorNoCursor for pagination
workflowIdNoFilter by workflow ID
statusNoFilter by status (success, error, running, warning)

Implementation Reference

  • Handles the 'n8n_list_executions' tool call by invoking the N8nClient's listExecutions method.
    case 'n8n_list_executions': {
      const result = await n8nClient.listExecutions({
        limit: (args?.limit as number) || 20,
        cursor: (args?.cursor as string),
        workflowId: args?.workflowId as string,
        status: args?.status as string,
      });
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
  • The underlying API implementation that executes the request to fetch workflow executions.
    async listExecutions(params?: {
      limit?: number;
      cursor?: string;
      workflowId?: string;
      status?: string;
    }): Promise<any> {
      const queryParams = new URLSearchParams();
      if (params?.limit) queryParams.append('limit', params.limit.toString());
      if (params?.cursor) queryParams.append('cursor', params.cursor);
      if (params?.workflowId) queryParams.append('workflowId', params.workflowId);
      if (params?.status) queryParams.append('status', params.status);
      const response = await this.client.get(`/executions?${queryParams}`);
      return response.data;
    }
  • Defines the input schema for the 'n8n_list_executions' tool.
    {
      name: 'n8n_list_executions',
      description: 'List workflow executions',
      inputSchema: {
        type: 'object',
        properties: {
          limit: { type: 'number', description: 'Number of executions to return (default: 20)' },
          cursor: { type: 'string', description: 'Cursor for pagination' },
          workflowId: { type: 'string', description: 'Filter by workflow ID' },
          status: { type: 'string', description: 'Filter by status (success, error, running, warning)' },
        },
      },
    },
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 but offers nothing beyond the action verb. It omits pagination behavior (despite cursor parameter), filtering logic, or whether executions include full run data versus metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the three-word description contains no fluff, it is under-informative rather than appropriately concise. It fails the 'every sentence earns its place' test by providing minimal value beyond the tool name itself.

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 four filterable parameters, zero annotations, no output schema, and a complex domain (workflow execution history), the description is inadequate. It should explain execution lifecycle context, filtering capabilities, or result set expectations.

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%, documenting all four parameters (limit, cursor, workflowId, status) including valid status values. The description adds no semantic context beyond the schema, warranting the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List workflow executions' is tautological—it merely converts the snake_case name to prose without adding specificity. It fails to distinguish from sibling n8n_get_execution (which retrieves a single execution) or clarify the listing scope.

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?

No guidance is provided on when to use this tool versus alternatives like n8n_get_execution (for specific records) or n8n_retry_execution (for failed runs). No prerequisites or exclusion criteria are mentioned.

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

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