n8n MCP Server

Overview Schema Source Related Servers Discussions Admin

Retry n8n Execution

n8n_retry_execution

Retry failed executions in n8n by creating a new run from the failure point. Optionally reload the current saved workflow for the retry.

Instructions

Retry a failed execution. Creates a new execution from the point of failure.

Args:

id (string): Failed execution ID to retry
loadWorkflowData (boolean): Reload workflow from current saved version (default false — uses original execution data)

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": "n8n_retry_execution"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Failed execution ID to retry
`loadWorkflowData`	No	Reload workflow from current saved version

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark this as non-read-only, but the description adds useful behavior details: it creates a new execution and clarifies that the default 'loadWorkflowData=false' uses original execution data. No contradiction 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 two concise sentences plus a compact arg list. Every sentence adds value, and the most important information (retry, from point of failure) is front-loaded.

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 2-parameter tool with no output schema, the description covers purpose, parameter behavior, and default semantics. It does not explain return values or errors, but those are less critical given the simple scope and existing annotations.

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 covers both parameters at 100%, but the description adds meaning for 'loadWorkflowData' by explaining the default's effect ('uses original execution data'), which goes beyond the schema's terser phrasing. This lifts it above the baseline.

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 'Retry' with the resource 'execution' and adds specificity with 'Creates a new execution from the point of failure'. This distinguishes it from sibling tools like list, get, stop, and delete executions.

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 gives clear context: use it for a failed execution. It does not explicitly mention alternatives or exclusions, but the 'failed execution' qualifier provides a clear trigger. Since it lacks any when-not guidance, it falls short of a 5.

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

Deploy Server