Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

List n8n Users

n8n_list_users
Read-onlyIdempotent

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

Instructions

List all users in the n8n instance.

Args:

  • includeRole (boolean): Include user roles (default: true)

  • limit (number): Maximum results (default: 100)

  • cursor (string, optional): Pagination cursor

Returns: List of users with id, email, name, and role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeRoleNoInclude user roles in response
limitNoMaximum results to return
cursorNoPagination cursor

Implementation Reference

  • The handler implementation for n8n_list_users.
    async (params: z.infer<typeof ListUsersSchema>) => {
      const queryParams: Record<string, unknown> = { 
        limit: params.limit,
        includeRole: params.includeRole
      };
      if (params.cursor) queryParams.cursor = params.cursor;
      
      const response = await get<N8nPaginatedResponse<N8nUser>>('/users', queryParams);
      
      const formatted = response.data.map(formatUser).join('\n\n---\n\n');
      const output = {
        count: response.data.length,
        users: response.data,
        nextCursor: response.nextCursor
      };
      
      let text = `Found ${response.data.length} user(s):\n\n${formatted}`;
      if (response.nextCursor) {
        text += `\n\n_More results available. Use cursor: ${response.nextCursor}_`;
      }
      
      return {
        content: [{ type: 'text', text }],
        structuredContent: output
      };
    }
  • Registration of the n8n_list_users tool.
      server.registerTool(
        'n8n_list_users',
        {
          title: 'List n8n Users',
          description: `List all users in the n8n instance.
    
    Args:
      - includeRole (boolean): Include user roles (default: true)
      - limit (number): Maximum results (default: 100)
      - cursor (string, optional): Pagination cursor
    
    Returns:
      List of users with id, email, name, and role.`,
          inputSchema: ListUsersSchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
          }
        },
Behavior3/5

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

Annotations already provide strong behavioral hints (readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false), so the bar is lower. The description adds some context by mentioning pagination via the cursor parameter and listing the return fields (id, email, name, role), which helps the agent understand the output format since there's no output schema. However, it doesn't disclose rate limits, authentication needs, or error conditions beyond what annotations imply.

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?

The description is well-structured and appropriately sized. It starts with the core purpose, then lists parameters and returns in clear sections. Every sentence adds value, though the parameter descriptions slightly overlap with the schema. It could be more front-loaded by moving the return details closer to the top for faster scanning.

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?

Given the tool's low complexity (simple list operation), rich annotations (covering safety and idempotency), and 100% schema coverage, the description is reasonably complete. It explains the return format, which is crucial since there's no output schema. However, it lacks context about authentication, error handling, or performance considerations that could help the agent use it more effectively.

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%, so the schema already fully documents all three parameters. The description adds minimal value beyond the schema: it restates the cursor's purpose ('Pagination cursor') and mentions the default for includeRole, but doesn't explain parameter interactions or provide usage examples. This meets the baseline for high 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?

The description clearly states the tool's purpose: 'List all users in the n8n instance.' This is a specific verb+resource combination that tells the agent exactly what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'n8n_get_user' (which presumably fetches a single user), so it misses the highest score.

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. With sibling tools like 'n8n_get_user' (for individual users) and 'n8n_get_current_user' (for the authenticated user), the agent receives no help in choosing between them. There's no mention of prerequisites, access requirements, or typical use cases.

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/DrBalls/n8n-mcp-server-v2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server