Skip to main content
Glama

n8n_list_variables

Retrieve all environment variables configured in your n8n instance to manage workflow configurations and settings.

Instructions

List all environment variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation in index.ts that calls n8nClient.listVariables().
    case 'n8n_list_variables': {
      const result = await n8nClient.listVariables();
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The underlying API client method that performs the GET request to /variables.
    async listVariables(): Promise<any> {
      const response = await this.client.get('/variables');
      return response.data;
    }
  • src/index.ts:661-668 (registration)
    Registration of the 'n8n_list_variables' tool in the tool list schema.
    {
      name: 'n8n_list_variables',
      description: 'List all environment variables',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

With zero annotations provided, the description carries the full burden of behavioral disclosure but fails to indicate whether the operation is read-only, whether sensitive values are masked, pagination behavior, or the return structure. 'List all' implies an unfiltered operation, but lacks critical safety and scope details.

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 brief at four words with no redundant phrasing or wasted sentences. Appropriately sized for the input complexity, though the extreme brevity limits informational value rather than demonstrating efficient information packing.

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 the absence of annotations and output schema, the description inadequately compensates by failing to describe return values, data structure, authentication requirements, or pagination limits. For a read operation with no inputs, minimum viable documentation would include the response format.

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?

Input schema contains zero parameters. Per evaluation guidelines, zero parameters establishes a baseline score of 4. The description does not need to compensate for undocumented parameters.

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?

The description provides a clear verb ('List') and resource ('environment variables'), distinguishing it from sibling tools that operate on workflows, users, projects, etc. However, it does not explicitly differentiate from related variable CRUD operations (create_variable, update_variable) or clarify scope beyond the word 'all'.

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 like create_variable or update_variable, or prerequisites such as required permissions. Single functional statement with no contextual usage advice.

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