Skip to main content
Glama

delete-workflow

Remove a workflow permanently by its ID using the n8n MCP Server. This action cannot be undone, so ensure you have the correct workflow identification before proceeding.

Instructions

Delete a workflow by ID. This action cannot be undone. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientIdYes
idYes

Implementation Reference

  • The execution handler for the 'delete-workflow' tool within the CallToolRequestSchema switch statement. It retrieves the N8nClient instance, calls deleteWorkflow(id), and returns success or error response.
    case "delete-workflow": {
      const { clientId, id } = args as { clientId: string; id: string };
      const client = clients.get(clientId);
      if (!client) {
        return {
          content: [{
            type: "text",
            text: "Client not initialized. Please run init-n8n first.",
          }],
          isError: true
        };
      }
    
      try {
        const workflow = await client.deleteWorkflow(id);
        return {
          content: [{
            type: "text",
            text: `Successfully deleted workflow:\n${JSON.stringify(workflow, null, 2)}`,
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: error instanceof Error ? error.message : "Unknown error occurred",
          }],
          isError: true
        };
      }
    }
  • src/index.ts:471-482 (registration)
    Registration of the 'delete-workflow' tool in the ListToolsRequestSchema handler, specifying name, description, and input schema.
    {
      name: "delete-workflow",
      description: "Delete a workflow by ID. This action cannot be undone. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.",
      inputSchema: {
        type: "object",
        properties: {
          clientId: { type: "string" },
          id: { type: "string" }
        },
        required: ["clientId", "id"]
      }
    },
  • N8nClient helper method that performs the actual DELETE API request to /workflows/{id}.
    async deleteWorkflow(id: string): Promise<N8nWorkflow> {
      return this.makeRequest<N8nWorkflow>(`/workflows/${id}`, {
        method: 'DELETE',
      });
    }
  • Input schema definition for the 'delete-workflow' tool, specifying required parameters clientId and id.
    inputSchema: {
      type: "object",
      properties: {
        clientId: { type: "string" },
        id: { type: "string" }
      },
      required: ["clientId", "id"]
    }
Behavior4/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. It effectively communicates the destructive nature ('This action cannot be undone') and provides important implementation guidance about argument formatting. However, it doesn't mention authentication requirements, rate limits, or what happens to dependent resources when a workflow is deleted.

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

Conciseness5/5

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

The description is extremely efficient with two sentences that each serve distinct purposes: the first states the core functionality, the second provides critical implementation guidance. There's zero wasted language, and the most important information (the irreversible deletion) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does well on behavioral warnings but poorly on parameter documentation. The irreversibility warning is crucial, but the complete lack of parameter semantics and absence of information about return values or error conditions leaves significant gaps for a tool that permanently deletes resources.

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?

With 0% schema description coverage for both parameters, the description provides no information about what 'clientId' or 'id' represent, their expected formats, or how they relate to workflow deletion. The description mentions 'ID' generally but doesn't clarify which parameter corresponds to the workflow ID versus client ID.

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 specific action ('Delete') and resource ('a workflow by ID'), distinguishing it from sibling tools like 'deactivate-workflow' or 'delete-project'. It provides a precise verb+resource combination that leaves no ambiguity about what the tool does.

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?

The description provides no guidance on when to use this tool versus alternatives like 'deactivate-workflow' or 'delete-execution'. While it warns about irreversibility, it doesn't specify prerequisites, conditions, or contextual factors that should influence tool selection among the many deletion-related siblings.

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

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