Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

n8n: Retry execution

n8n_retry_execution
Destructive

Retry a failed execution by creating a new execution with the same input data, helping recover from transient errors or failed runs.

Instructions

[UNIFIED] Retry a failed execution. Creates a new execution with the same input 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": {
      "site": "<site>",
      "execution_id": "<execution_id>"
    },
    "name": "n8n_retry_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
execution_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true; the description adds the reason, explaining that a brand-new execution is created from the same input data, which tells the agent the workflow will re-run and repeat its external side effects. It stops short of covering permissions, what happens if the execution did not fail, or how failures during retry are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the action and the effect front-loaded; nothing is wasted. The '[UNIFIED]' prefix is minor noise that adds no meaning for an agent.

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?

For a destructive, non-idempotent action tool with no output schema and two undocumented parameters, the definition is thin: it does not say what is returned (presumably the new execution ID) or define 'site'. An agent can guess the intent but not the full calling contract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters, so the description must compensate and it does not. 'execution_id' is inferable, but 'site' is never explained (instance/tenant selector? URL?), leaving the agent to guess what value to supply.

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?

States a specific verb and resource: retry a failed execution, plus the mechanism (a new execution with the same input data). An agent can distinguish it from read-oriented siblings like n8n_get_execution or n8n_stop_execution, though it never explicitly contrasts itself with n8n_execute_workflow or n8n_execute_workflow_with_data, which could look similar.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'a failed execution' implies the precondition for use, but there is no explicit when-to-use/when-not guidance and no named alternative for re-running a workflow from scratch. The agent must infer that the target execution must be in a failed state.

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

Deploy Server

Other Tools