Skip to main content
Glama

n8n_create_variable

Create environment variables in n8n to store configuration values for workflows, supporting string, number, boolean, and JSON data types.

Instructions

Create a new environment variable

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesVariable key
valueYesVariable value
typeNoVariable type (string, number, boolean, json)

Implementation Reference

  • The core API call implementation for creating an n8n variable.
    async createVariable(data: { key: string; value: string; type?: string }): Promise<any> {
      const response = await this.client.post('/variables', data);
      return response.data;
    }
  • The request handler for the n8n_create_variable tool, which processes arguments and calls the n8n client.
    case 'n8n_create_variable': {
      if (!args?.key || !args?.value) {
        throw new Error('key and value are required');
      }
      const result = await n8nClient.createVariable(args as any);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • src/index.ts:670-681 (registration)
    The tool definition and schema registration for n8n_create_variable.
      name: 'n8n_create_variable',
      description: 'Create a new environment variable',
      inputSchema: {
        type: 'object',
        properties: {
          key: { type: 'string', description: 'Variable key' },
          value: { type: 'string', description: 'Variable value' },
          type: { type: 'string', description: 'Variable type (string, number, boolean, json)' },
        },
        required: ['key', 'value'],
      },
    },
Behavior2/5

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

No annotations provided, so description must carry full burden. It states the mutation type (create) but omits critical safety details: idempotency, error conditions (e.g., duplicate key handling), return values, or whether the variable is instance-scoped or project-scoped.

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?

Single sentence front-loads the core action. No wasted words, though brevity crosses into under-specification given the mutation complexity and lack of annotations.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks error handling details, conflict resolution behavior (crucial for 'create' operations), and relationship to other variable lifecycle tools.

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%, documenting all three parameters (key, value, type) adequately. The description adds no additional semantic clarity (e.g., format constraints, examples) but baseline 3 is appropriate given complete schema coverage.

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 ('Create') and resource ('environment variable') with specific scope indicated by 'envrionment.' However, it fails to explicitly distinguish from sibling n8n_update_variable or clarify behavior if the variable already exists.

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 on when to use this versus n8n_update_variable, nor prerequisites (e.g., whether the variable key must be unique, required permissions, or project scoping).

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