Skip to main content
Glama

n8n_delete_execution

Remove workflow executions from n8n by specifying an execution ID to manage execution history and maintain system performance.

Instructions

Delete an execution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesExecution ID to delete

Implementation Reference

  • The N8nClient method that performs the actual API call to delete an execution.
    async deleteExecution(id: string): Promise<any> {
      const response = await this.client.delete(`/executions/${id}`);
      return response.data;
    }
  • The tool handler in the main MCP entry point that receives the request and calls the N8nClient.
    case 'n8n_delete_execution': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.deleteExecution(args.id as string);
      return {
        content: [{ type: 'text', text: `Execution ${args.id as string} deleted successfully` }],
      };
    }
  • The tool registration definition which includes the input schema for the n8n_delete_execution tool.
    name: 'n8n_delete_execution',
    description: 'Delete an execution',
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Execution ID to delete' },
      },
      required: ['id'],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'delete' implies destruction, the description fails to clarify if deletion is permanent, whether it affects associated workflow data or logs, or if there are rate limits/permissions required for this destructive operation.

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?

The description is extremely brief (3 words), which prevents verbosity, but it fails to earn its place by providing actionable intelligence. The front-loading is technically present but content-deficient for a destructive operation requiring safety context.

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 operation with no annotations and no output schema, the description is inadequate. It lacks critical safety warnings about permanence, lacks clarification on whether deleted executions can be retrieved, and omits any mention of side effects or required execution states (e.g., finished vs running).

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 description coverage is 100%, with the 'id' parameter already documented as 'Execution ID to delete' in the schema. The description adds no additional semantic value regarding parameter format, validation rules, or constraints beyond what the schema already provides, warranting the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete an execution' is essentially a tautology that restates the tool name (n8n_delete_execution) without adding specificity. While it indicates a deletion operation, it fails to distinguish from sibling execution tools like n8n_retry_execution or clarify what type of execution (workflow execution) is being targeted.

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

Usage Guidelines1/5

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

No guidance provided on when to use this tool versus alternatives like n8n_retry_execution or n8n_get_execution. No warnings about prerequisites (e.g., execution state requirements) or irreversible consequences are mentioned.

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