Skip to main content
Glama

n8n_retry_execution

Retry failed workflow executions in n8n by specifying the execution ID to restart and complete previously unsuccessful operations.

Instructions

Retry a failed execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesExecution ID to retry

Implementation Reference

  • The actual HTTP request implementation for retrying an n8n execution.
    async retryExecution(id: string): Promise<any> {
      const response = await this.client.post(`/executions/${id}/retry`);
      return response.data;
    }
  • src/index.ts:601-610 (registration)
    Tool registration for n8n_retry_execution.
    {
      name: 'n8n_retry_execution',
      description: 'Retry a failed execution',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Execution ID to retry' },
        },
        required: ['id'],
      },
  • Tool handler logic which calls the n8n client.
    case 'n8n_retry_execution': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.retryExecution(args.id as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
Behavior2/5

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

No annotations provided, so description carries full burden. 'Retry' implies mutation but lacks disclosure: whether it creates a new execution ID or reuses existing, if it waits for completion, valid terminal states for retry, or side effects on execution history. No mention of idempotency or rate limits.

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

Conciseness3/5

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

Extremely brief (4 words) and front-loaded, but sacrifices necessary behavioral detail for brevity. Under-specified rather than appropriately concise given the operational complexity of execution retry logic.

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 an execution retry operation, lacks critical context: whether it returns the new execution details, how it relates to the original execution record, and operational constraints. Simple schema with 1 parameter does not excuse missing behavioral context for workflow engine operations.

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 coverage is 100% with clear parameter description ('Execution ID to retry'). Description does not add parameter syntax, format constraints, or examples beyond schema, but baseline 3 is appropriate given complete schema documentation.

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 (Retry) and resource (execution), with scope limitation (failed). Distinct from siblings like get_execution, delete_execution, and list_executions by specifying the retry action and failed-state precondition.

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?

No guidance on when to use vs alternatives, prerequisites (e.g., execution must be in terminal failed state), or when not to use (e.g., cannot retry running executions). Missing error handling 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/Shravan1610/n8n-mcp-server'

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