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, ];

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