Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

delete_execution

Delete a specific workflow execution by its ID to remove it from n8n execution history. Useful for cleaning up unfinished or failed runs.

Instructions

Delete an execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
executionIdYesThe ID of the execution to delete

Implementation Reference

  • Handler case in the tool dispatch switch. Validates args using ExecutionIdSchema (extracting executionId) and calls client.deleteExecution(executionId).
    case "delete_execution": {
      const { executionId } = ExecutionIdSchema.parse(args);
      return await client.deleteExecution(executionId);
    }
  • Zod schema used to validate the input arguments for delete_execution (and other execution-related tools). Expects a string 'executionId'.
    const ExecutionIdSchema = z.object({
      executionId: z.string(),
    });
  • src/tools.ts:221-233 (registration)
    Tool definition/registration for 'delete_execution' with description and inputSchema requiring an 'executionId' string.
    {
      name: "delete_execution",
      description: "Delete an execution",
      inputSchema: {
        type: "object",
        properties: {
          executionId: {
            type: "string",
            description: "The ID of the execution to delete",
          },
        },
        required: ["executionId"],
      },
  • Actual API call to the n8n backend. Sends a DELETE request to /api/v1/executions/{id} and returns a success message.
    async deleteExecution(id: string) {
      await this.client.delete(`/api/v1/executions/${id}`);
      return { success: true, message: `Execution ${id} deleted successfully` };
    }
Behavior2/5

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

No annotations, so description carries full burden. 'Delete' implies destruction, but no details on irreversibility, effects on related data, or failure conditions. Minimal transparency.

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

Conciseness2/5

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

Extremely concise with only three words, but at the expense of completeness. It is front-loaded but lacks structure and detail.

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 simple tool with 1 parameter and no output schema, the description is too minimal. It omits return behavior, error states, and side effects, leaving the agent without full context.

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% and the single parameter 'executionId' is well-described in the schema. The description adds no additional meaning beyond the schema.

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?

Clearly states the verb 'Delete' and resource 'execution', making the primary action unambiguous. However, it does not specify what type of execution (e.g., workflow execution), though sibling tools provide context.

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 this tool versus alternatives like 'retry_execution' or 'get_execution'. No prerequisites or context provided.

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