n8n-free-mcp

Get execution

get_execution

Retrieve execution details including per-node data with includeData=true to diagnose errors.

Instructions

Get the details of an execution. With includeData=true it returns per-node data (can be very large) — ideal for diagnosing errors.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_execution"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Execution ID
`includeData`	No	Include node input/output data (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 4, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description covers the key behavioral trait of large data when includeData=true. However, it does not mention idempotency, safety, or access requirements, which are minimal for a read operation.

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?

Two concise sentences front-loading the purpose, with no wasted words. Every sentence adds value.

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?

The description covers the tool's core behavior adequately given the simple 2-parameter schema and no output schema. It explains the critical parameter behavior but could optionally mention return structure.

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%, providing baseline of 3. The description adds value by explaining that includeData=true returns per-node data and is useful for error diagnosis, going beyond the schema's basic 'include node input/output data'.

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 verb 'Get' and the resource 'execution details', distinguishing it from siblings like 'list_executions' and 'delete_execution'. It adds specificity about the includeData parameter differentiating it from a basic list.

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 advises using includeData=true for diagnosing errors and warns about potential large data size, providing clear usage context. It does not explicitly mention when to avoid it, but the warning implies caution.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server