Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

retry_execution

Retry a failed workflow execution by providing its execution ID.

Instructions

Retry a failed execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
executionIdYesThe ID of the execution to retry

Implementation Reference

  • Handler case for retry_execution tool - parses executionId from args using ExecutionIdSchema and calls client.retryExecution()
    case "retry_execution": {
      const { executionId } = ExecutionIdSchema.parse(args);
      return await client.retryExecution(executionId);
    }
  • Zod schema for input validation - requires a string executionId
    const ExecutionIdSchema = z.object({
      executionId: z.string(),
    });
  • src/tools.ts:235-248 (registration)
    Tool registration definition with name 'retry_execution', description, and inputSchema (object with required string executionId)
    {
      name: "retry_execution",
      description: "Retry a failed execution",
      inputSchema: {
        type: "object",
        properties: {
          executionId: {
            type: "string",
            description: "The ID of the execution to retry",
          },
        },
        required: ["executionId"],
      },
    },
  • Actual HTTP call: POST to /api/v1/executions/{id}/retry to retry a failed execution
    async retryExecution(id: string) {
      const response = await this.client.post(`/api/v1/executions/${id}/retry`);
      return response.data;
    }
Behavior2/5

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

No annotations exist, and the description does not disclose what 'retry' entails—e.g., whether it creates a new execution, requires specific permissions, or if it has side effects. Behavioral details are absent.

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?

The description is a single short sentence with no wasted words, but it could be slightly expanded to include behavioral context without losing conciseness.

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 tool with no output schema and simple parameters, the description does not explain what the tool returns or any side effects, leaving the agent underinformed.

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% for the single parameter 'executionId', and the description adds no meaning beyond it. Baseline score of 3 is appropriate.

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 action ('Retry') and the resource ('failed execution'), making it distinct from siblings like execute_workflow (new) and delete_execution (remove).

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 is provided on when to use this tool vs. alternatives, such as when an execution failed or what prerequisites are needed. The usage context is only implied.

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

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