Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get n8n Execution

n8n_get_execution
Read-onlyIdempotent

Retrieve detailed execution information including status, timestamps, workflow data, and node outputs using an execution ID.

Instructions

Get detailed information about a specific execution.

Args:

  • id (string): Execution ID

  • includeData (boolean): Include full execution data with node outputs (default: true)

Returns: Complete execution details including:

  • Status and mode

  • Timestamps (started, stopped)

  • Workflow data

  • Node execution results (if includeData is true)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesExecution ID
includeDataNoInclude full execution data

Implementation Reference

  • src/tools/executions.ts:99-142 (handler)
    The tool 'n8n_get_execution' is registered and implemented here. It retrieves detailed execution information from the n8n API using the provided execution ID and includeData flag.
      server.registerTool(
    'n8n_get_execution',
    {
      title: 'Get n8n Execution',
      description: `Get detailed information about a specific execution.

Args:
  - id (string): Execution ID
  - includeData (boolean): Include full execution data with node outputs (default: true)

Returns:
  Complete execution details including:
  - Status and mode
  - Timestamps (started, stopped)
  - Workflow data
  - Node execution results (if includeData is true)`,
      inputSchema: GetExecutionSchema,
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false
      }
    },
    async (params: z.infer<typeof GetExecutionSchema>) => {
      const execution = await get<N8nExecution>(`/executions/${params.id}`, {
        includeData: params.includeData
      });
      
      let text = formatExecution(execution);
      
      if (execution.data?.resultData?.error) {
        text += `\n\n**Error:**\n\`\`\`\n${JSON.stringify(execution.data.resultData.error, null, 2)}\n\`\`\``;
      }
      
      if (execution.data?.resultData?.lastNodeExecuted) {
        text += `\n\n- Last Node: ${execution.data.resultData.lastNodeExecuted}`;
      }
      
      return {
        content: [{ type: 'text', text }],
        structuredContent: execution
      };
    }

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds valuable context beyond annotations by specifying what information is returned (status, timestamps, workflow data, node results) and the conditional inclusion of node outputs based on includeData. No contradictions with annotations.

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 well-structured and front-loaded with the core purpose. Every sentence adds value: the first states the action, the Args section clarifies parameters, and the Returns section details output content. No redundant or verbose language.

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?

For a read-only tool with good annotations and no output schema, the description is mostly complete: it covers purpose, parameters, and return details. However, it lacks information on error conditions (e.g., what happens if the ID is invalid) and doesn't mention pagination or rate limits, which could be relevant for execution data.

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%, with clear parameter documentation in the schema. The description adds minimal value beyond the schema: it restates the purpose of includeData ('Include full execution data with node outputs') but doesn't provide additional semantic context like examples or edge cases. Baseline 3 is appropriate given high schema coverage.

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 the specific action ('Get detailed information about a specific execution') and distinguishes it from sibling tools like 'n8n_list_executions' (which lists multiple executions) and 'n8n_delete_execution' (which deletes rather than retrieves). The verb 'Get' is precise and the resource 'execution' is well-defined.

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 implies usage context by specifying 'a specific execution' (requiring an ID), but doesn't explicitly state when to use this versus alternatives like 'n8n_list_executions' for browsing or 'n8n_get_workflow' for workflow metadata. It provides clear prerequisites (needs an execution ID) but lacks explicit exclusion guidance.

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

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