Skip to main content
Glama

n8n_delete_variable

Remove an environment variable from n8n workflows by specifying its ID to manage configuration settings.

Instructions

Delete an environment variable

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVariable ID to delete

Implementation Reference

  • The n8nClient implementation that performs the HTTP DELETE request to delete a variable.
    async deleteVariable(id: string): Promise<any> {
      const response = await this.client.delete(`/variables/${id}`);
      return response.data;
    }
  • The tool handler switch case in src/index.ts that invokes n8nClient.deleteVariable.
    case 'n8n_delete_variable': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.deleteVariable(args.id as string);
      return {
        content: [{ type: 'text', text: `Variable ${args.id as string} deleted successfully` }],
      };
    }
  • The tool schema definition for n8n_delete_variable.
    {
      name: 'n8n_delete_variable',
      description: 'Delete an environment variable',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Variable ID to delete' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Delete' implies destruction, it fails to disclose whether deletion is permanent, if it affects running workflows, or whether authorization checks occur. No mention of error conditions (e.g., if ID not found).

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

Conciseness4/5

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

Extremely concise (4 words) with no redundancy. However, brevity crosses into under-specification given the lack of annotations and destructive nature of the operation.

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?

Adequate for a single-parameter CRUD operation with complete schema coverage, but gaps remain: no output schema explanation (though not required), no safety confirmation patterns, and no linkage to sibling variable tools for full workflow context.

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 coverage is 100% with 'id' fully described as 'Variable ID to delete'. Description adds no additional semantics, examples, or format constraints beyond the schema, warranting baseline score.

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

Purpose4/5

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

Clear verb 'Delete' and resource 'environment variable' identify the operation. However, it does not distinguish from sibling variable operations (create, update, list) or clarify when deletion is preferable to updating versus creating.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., when to delete vs update a variable) or prerequisites (e.g., checking if variable is in use). No safety warnings or exclusion criteria 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