Skip to main content
Glama

n8n_list_users

Retrieve all user accounts from your n8n instance to manage access and permissions.

Instructions

List all users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `listUsers` method in the N8nClient class.
    async listUsers(): Promise<any> {
      const response = await this.client.get('/users');
      return response.data;
    }
  • src/index.ts:762-769 (registration)
    The registration of the `n8n_list_users` tool.
    {
      name: 'n8n_list_users',
      description: 'List all users',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The handler logic that calls `n8nClient.listUsers()` when `n8n_list_users` tool is requested.
    case 'n8n_list_users': {
      const result = await n8nClient.listUsers();
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
Behavior2/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, yet reveals nothing about whether this is a read-only operation, what user attributes are exposed, if results are paginated, or potential rate limits for bulk user queries.

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

Conciseness3/5

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

While the three-word description avoids verbosity, it borders on under-specification. It fails to front-load critical context about the scope of 'all users' (instance-wide vs. project-specific) or the expected return structure that would help an agent invoke the tool confidently.

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 presence of complex user management siblings (n8n_update_user_role, n8n_add_user_to_project) and the absence of an output schema, the description is inadequate. It lacks explanation of user entity relationships, filtering capabilities, or output format that an agent would need to effectively utilize the returned user list.

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 input schema contains zero parameters. Per calibration guidelines, this establishes a baseline score of 4, as there are no parameter semantics requiring description beyond the empty schema structure.

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

Purpose3/5

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

The description states the basic verb (List) and resource scope (all users), but fails to distinguish this tool from sibling 'n8n_get_user'. Given that both tools involve user retrieval, the description should clarify that this returns a collection of all users versus retrieving a specific individual.

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?

The description provides no guidance on when to use this tool versus alternatives (like n8n_get_user), nor does it mention prerequisites such as administrative privileges typically required for listing users in n8n systems.

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