Skip to main content
Glama

n8n_get_execution

Retrieve detailed execution data including input/output information for n8n workflow analysis and debugging.

Instructions

Get detailed information about a specific execution including input/output data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe execution ID
includeDataNoInclude full execution data (default: true)

Implementation Reference

  • The main handler function for the n8n_get_execution tool. It validates input, calls the N8nApiClient to fetch execution data, formats the response, and returns it as JSON.
    n8n_get_execution: async (
      client: N8nApiClient,
      args: Record<string, unknown>
    ): Promise<ToolResult> => {
      const id = args.id as string;
      if (!id) {
        throw new Error('Execution ID is required');
      }
    
      const includeData = args.includeData !== false; // default true
      const execution = await client.getExecution(id, includeData);
    
      const response: Record<string, unknown> = {
        id: execution.id,
        workflowId: execution.workflowId,
        status: execution.status,
        mode: execution.mode,
        startedAt: execution.startedAt,
        stoppedAt: execution.stoppedAt,
        finished: execution.finished,
      };
    
      if (includeData && execution.data) {
        response.data = execution.data;
      }
    
      if (execution.data?.resultData?.error) {
        response.error = execution.data.resultData.error;
      }
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    },
  • Tool definition schema including name, description, and input validation schema for the n8n_get_execution tool.
    {
      name: 'n8n_get_execution',
      description: 'Get detailed information about a specific execution including input/output data.',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'The execution ID',
          },
          includeData: {
            type: 'boolean',
            description: 'Include full execution data (default: true)',
          },
        },
        required: ['id'],
      },
    },
  • src/server.ts:127-131 (registration)
    Registration and dispatch logic in the MCP server that routes calls to n8n_get_execution and other execution tool handlers.
    // Execution tools
    if (name in executionToolHandlers) {
      const handler = executionToolHandlers[name as keyof typeof executionToolHandlers];
      return handler(client, args);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool retrieves 'detailed information' and 'input/output data', but lacks critical details such as whether this is a read-only operation, any authentication requirements, rate limits, error handling, or the format of the returned data. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes essential information, earning its place.

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 the complexity of retrieving execution data, the lack of annotations and output schema means the description should do more to compensate. It doesn't explain what 'detailed information' includes beyond input/output data, nor does it cover behavioral aspects like safety or response format. For a tool with no structured support, this description is incomplete and leaves the agent with insufficient context.

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 both parameters ('id' and 'includeData') with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as examples or context for when to set 'includeData' to false. Baseline 3 is appropriate when the schema handles parameter documentation effectively.

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 with a specific verb ('Get') and resource ('detailed information about a specific execution'), including the scope of data (input/output). It distinguishes from siblings like 'n8n_list_executions' by focusing on a single execution rather than listing multiple. However, it doesn't explicitly contrast with 'n8n_get_workflow' or 'n8n_get_node_info', which slightly limits differentiation.

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 doesn't mention prerequisites (e.g., needing an execution ID from 'n8n_list_executions'), exclusions, or comparisons to siblings like 'n8n_get_workflow' for workflow-level details. Usage is implied by the name and parameters but not explicitly stated.

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/alicankiraz1/cursor-n8n-builder'

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