Skip to main content
Glama
Sign In
n8n-free-mcp

n8n-free-mcp

by justineserna1z
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Delete workflow

delete_workflow

Permanently remove a workflow from your n8n instance using its ID. This action is irreversible; confirm with the user before execution.

Instructions

Permanently delete a workflow. ⚠️ Irreversible — confirm with the user before using.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "delete_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the workflow to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that deletion is permanent and irreversible, which is critical. However, it could mention prerequisites (e.g., workflow state) or what happens to associated data.

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?

Two concise sentences with zero fluff. The warning emoji adds emphasis without waste.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation, the description is fairly complete: it states action, permanence, and required confirmation. Could optionally mention return value or error cases, but not essential.

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% (id parameter described in schema). The description adds no extra meaning to the parameter, so baseline 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 'Permanently delete a workflow', which is a specific verb-resource pair. This distinguishes it from siblings like deactivate_workflow (temporary) and delete_execution (different resource).

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

Usage Guidelines4/5

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

The description provides a clear guideline: 'confirm with the user before using' and notes irreversibility. However, it does not explicitly list alternatives or when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools