Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

get_executions

Retrieve workflow execution history with filters by workflow ID, status, limit, and cursor for pagination.

Instructions

Get workflow execution history with filtering options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdNoFilter by workflow ID
finishedNoFilter by execution status
limitNoMaximum number of executions to return
cursorNoCursor for pagination

Implementation Reference

  • The handler case in the switch statement that processes the 'get_executions' tool call. It validates input via GetExecutionsSchema and delegates to the client's getExecutions method.
    case "get_executions": {
      const params = GetExecutionsSchema.parse(args);
      return await client.getExecutions(params);
    }
  • Zod schema (GetExecutionsSchema) that validates the input parameters for the 'get_executions' tool: optional workflowId, finished, limit (default 10), and cursor.
    const GetExecutionsSchema = z.object({
      workflowId: z.string().optional(),
      finished: z.boolean().optional(),
      limit: z.number().optional().default(10),
      cursor: z.string().optional(),
    });
  • src/tools.ts:181-206 (registration)
    The tool definition/registration in the tools array, including its name 'get_executions', description, and inputSchema with properties for workflowId, finished, limit, and cursor.
    {
      name: "get_executions",
      description: "Get workflow execution history with filtering options",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "Filter by workflow ID",
          },
          finished: {
            type: "boolean",
            description: "Filter by execution status",
          },
          limit: {
            type: "number",
            description: "Maximum number of executions to return",
            default: 10,
          },
          cursor: {
            type: "string",
            description: "Cursor for pagination",
          },
        },
      },
    },
  • The N8nClient.getExecutions method that makes the actual HTTP GET request to /api/v1/executions with query parameters and returns the response data.
    async getExecutions(params?: {
      workflowId?: string;
      finished?: boolean;
      limit?: number;
      cursor?: string;
    }) {
      const response = await this.client.get("/api/v1/executions", { params });
      return response.data;
    }
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits like read-only nature, authentication requirements, or side effects. 'Get' implies read-only but is not explicit.

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 sentence, concise with no wasted words. However, it could be slightly more structured to mention pagination or ordering.

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?

Missing information about pagination (cursor, limit defaults), ordering, and the distinction from 'get_execution' (singular). Given no output schema, the description should cover return format but does not.

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%, so the schema already documents all parameters. The description adds the phrase 'filtering options' but does not provide additional meaning beyond the schema.

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

Purpose5/5

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

The description clearly states 'Get workflow execution history with filtering options', specifying a clear verb and resource. It distinguishes from singular 'get_execution' and other siblings like 'delete_execution'.

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 on when to use this tool versus alternatives such as 'get_execution' (singular) or 'retry_execution'. The description lacks explicit when-to-use or when-not-to-use context.

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

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