Skip to main content
Glama
AutomateLab-tech

automatelab-n8n-mcp

n8n_list_executions

Retrieve recent n8n workflow executions. Filter by workflow ID, status (success, error, waiting), or limit results. Optionally include full execution data for diagnosing failures.

Instructions

List recent executions from a live n8n instance (requires N8N_API_URL + N8N_API_KEY). Filter by workflowId, status (success|error|waiting), limit. Pass includeData: true to get the full execution body (large) — pair with n8n_explain_execution to diagnose a specific failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdNoFilter by workflow ID.
statusNoFilter by status: success | error | waiting.
limitNoPage size (n8n default: 100, max: 250).
includeDataNoInclude full execution data (large). Default false — pair with n8n_explain_execution.

Implementation Reference

  • src/index.ts:88-93 (registration)
    Registration of the 'n8n_list_executions' tool in the tools array with its name, description, and inputSchema.
    {
    	name: "n8n_list_executions",
    	description:
    		"List recent executions from a live n8n instance (requires N8N_API_URL + N8N_API_KEY). Filter by workflowId, status (success|error|waiting), limit. Pass `includeData: true` to get the full execution body (large) — pair with n8n_explain_execution to diagnose a specific failure.",
    	inputSchema: listExecutionsInputSchema,
    },
  • Handler function 'listExecutions' that executes the n8n_list_executions tool logic — parses arguments, builds query params, calls the n8n REST API GET /executions, and returns either full data or a summary.
    export async function listExecutions(rawArgs: unknown) {
    	const cfg = getConfig();
    	if ("error" in cfg) return textResult(cfg.error);
    	const args = listExecutionsZod.parse(rawArgs ?? {});
    	const params = new URLSearchParams();
    	if (args.workflowId) params.set("workflowId", args.workflowId);
    	if (args.status) params.set("status", args.status);
    	if (args.limit) params.set("limit", String(args.limit));
    	if (args.includeData) params.set("includeData", "true");
    	const qs = params.toString() ? `?${params}` : "";
    	const r = await call(cfg, "GET", `/executions${qs}`);
    	if (!r.ok) return textResult(r.error);
    	if (args.includeData) return jsonResult(r.data);
    	const data = r.data as { data?: unknown[] } | unknown[];
    	const arr = Array.isArray(data) ? data : data?.data ?? [];
    	const summary = (arr as Array<Record<string, unknown>>).map((e) => ({
    		id: e.id,
    		workflowId: e.workflowId,
    		status: e.status,
    		mode: e.mode,
    		startedAt: e.startedAt,
    		stoppedAt: e.stoppedAt,
    		finished: e.finished,
    	}));
    	return jsonResult(summary);
    }
  • Input schema (Zod) for validation of the listExecutions arguments: workflowId, status, limit, includeData.
    const listExecutionsZod = z.object({
    	workflowId: z.string().optional(),
    	status: z.enum(["success", "error", "waiting"]).optional(),
    	limit: z.number().int().positive().max(250).optional(),
    	includeData: z.boolean().optional(),
    });
  • JSON Schema input schema for listExecutions (used in MCP tool registration).
    export const listExecutionsInputSchema = {
    	type: "object",
    	properties: {
    		workflowId: { type: "string", description: "Filter by workflow ID." },
    		status: {
    			type: "string",
    			description: "Filter by status: success | error | waiting.",
    			enum: ["success", "error", "waiting"],
    		},
    		limit: {
    			type: "number",
    			description: "Page size (n8n default: 100, max: 250).",
    		},
    		includeData: {
    			type: "boolean",
    			description:
    				"Include full execution data (large). Default false — pair with n8n_explain_execution.",
    		},
    	},
    } as const;
  • src/index.ts:127-128 (registration)
    Case branch in the CallToolRequestSchema handler that dispatches to the listExecutions function.
    case "n8n_list_executions":
    	return listExecutions(args ?? {});
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that includeData returns large data, which is a key behavioral trait. However, it does not explicitly state read-only nature, error handling, or rate limits, which would be beneficial for a complete picture.

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 concise consisting of two sentences. It front-loads the purpose and includes essential details about parameters and usage without redundancy.

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 lack of an output schema, the description provides sufficient context: it covers filtering, large data warnings, and a pairing suggestion. It does not mention pagination or response structure, but for a list tool with limit parameter, it is reasonably complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the large data implication of includeData, providing defaults and constraints for limit, and listing status options. This goes beyond the schema alone.

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 it lists recent executions from a live n8n instance, includes required environment variables, and mentions filtering options. It distinguishes itself from sibling tools by specifying it's for executions, not workflows, and pairs it with n8n_explain_execution for diagnosis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool (listing recent executions), provides filtering parameters, and advises against using includeData unnecessarily due to large data. It also suggests pairing with n8n_explain_execution for specific failure diagnosis, giving clear usage 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/AutomateLab-tech/n8n-mcp'

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