Skip to main content
Glama

delete-variable

Remove a variable from n8n workflows by specifying its ID. Requires n8n Enterprise license with variable management enabled. Use after listing variables to identify the correct ID. This action is permanent and cannot be reversed.

Instructions

Delete a variable by ID. NOTE: Requires n8n Enterprise license with variable management features enabled. Use after list-variables to get the ID of the variable to delete. 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

  • MCP tool handler for 'delete-variable' that retrieves the N8nClient by clientId and calls its deleteVariable method to delete the variable by ID via the n8n API.
    case "delete-variable": {
      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 {
        await client.deleteVariable(id);
        return {
          content: [{
            type: "text",
            text: `Successfully deleted variable with ID: ${id}`,
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: error instanceof Error ? error.message : "Unknown error occurred",
          }],
          isError: true
        };
      }
    }
  • Input schema definition for the delete-variable tool, specifying clientId and id as required string parameters.
    inputSchema: {
      type: "object",
      properties: {
        clientId: { type: "string" },
        id: { type: "string" }
      },
      required: ["clientId", "id"]
    }
  • src/index.ts:639-650 (registration)
    Registration of the 'delete-variable' tool in the ListToolsRequestSchema handler's tools array, including name, description, and input schema.
    {
      name: "delete-variable",
      description: "Delete a variable by ID. NOTE: Requires n8n Enterprise license with variable management features enabled. Use after list-variables to get the ID of the variable to delete. 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 makes a DELETE request to the n8n API endpoint /variables/{id} to delete the specified variable.
    async deleteVariable(id: string): Promise<void> {
      return this.makeRequest<void>(`/variables/${id}`, {
        method: 'DELETE',
      });
Behavior5/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 successfully describes critical behavioral traits: the irreversible nature of the operation ('This action cannot be undone'), specific licensing requirements ('Requires n8n Enterprise license'), and input format constraints ('Arguments must be provided as compact, single-line JSON without whitespace or newlines'). This covers safety, prerequisites, and technical constraints.

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 perfectly structured and front-loaded with the core purpose, followed by important notes in logical order (prerequisites, usage guidance, warnings, technical requirements). Every sentence earns its place with critical information, and there's zero wasted text or redundancy.

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 destructive tool with no annotations and no output schema, the description does an excellent job covering behavioral aspects (irreversible, licensing, input format) and usage guidance. The main gap is incomplete parameter documentation (only explains 'id', not 'clientId'), which prevents a perfect score despite otherwise comprehensive coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description must compensate. It explains that the 'id' parameter refers to 'the ID of the variable to delete' and implies it should come from 'list-variables'. However, it doesn't explain the 'clientId' parameter at all. The description adds meaningful context for one parameter but leaves the other undocumented.

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 a variable by ID') with the exact resource ('variable'), distinguishing it from sibling tools like 'delete-workflow', 'delete-user', or 'delete-tag' that target different resources. It uses precise language 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 Guidelines5/5

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

The description provides explicit guidance on when to use this tool ('Use after list-variables to get the ID of the variable to delete') and mentions prerequisites ('Requires n8n Enterprise license with variable management features enabled'). It also clearly states when NOT to use it ('This action cannot be undone'), providing complete usage context.

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