Skip to main content
Glama

n8n_delete_workflow

Remove a workflow from n8n by specifying its ID to manage automation processes and maintain organized workflow libraries.

Instructions

Delete a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWorkflow ID to delete

Implementation Reference

  • The actual API call to delete a workflow.
    async deleteWorkflow(id: string): Promise<any> {
      const response = await this.client.delete(`/workflows/${id}`);
      return response.data;
    }
  • MCP tool handler logic for n8n_delete_workflow.
    case 'n8n_delete_workflow': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.deleteWorkflow(args.id as string);
      return {
        content: [{ type: 'text', text: `Workflow ${args.id as string} deleted successfully` }],
      };
    }
  • Tool registration and input schema for n8n_delete_workflow.
    name: 'n8n_delete_workflow',
    description: 'Delete a workflow',
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string', description: 'Workflow ID to delete' },
      },
      required: ['id'],
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to clarify whether deletion is permanent or reversible, what happens to associated executions/tags, or required permissions. The word 'Delete' implies destruction but lacks critical safety context for a 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) and front-loaded, but for a destructive operation lacks necessary detail. It suffers from under-specification rather than efficient conciseness—too minimal to safely guide agent invocation.

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?

Given this is a destructive operation with no annotations and no output schema, the description should disclose behavioral risks, cascades, or return status. The current description is insufficiently complete for safe agent operation.

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?

With 100% schema description coverage ('Workflow ID to delete'), the schema adequately documents the single parameter. The description adds no additional semantic value regarding the parameter format or constraints, but baseline 3 is appropriate given the complete schema coverage.

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 a workflow' is tautological, simply restating the tool name without the 'n8n_' prefix. While it identifies the verb and resource, it fails to distinguish this from sibling deletion tools (n8n_delete_credential, n8n_delete_execution, etc.) or specify scope.

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 provided on when to use this tool versus alternatives, prerequisites (e.g., workflow must exist), or warnings about dependencies. The description lacks any usage constraints or conditions.

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