Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

Get n8n User

n8n_get_user
Read-onlyIdempotent

Retrieve user details including ID, email, name, and role from the n8n automation platform using a unique identifier.

Instructions

Get details of a specific user.

Args:

  • id (string): User ID

Returns: User details with id, email, name, and role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the resource

Implementation Reference

  • Implementation of the n8n_get_user MCP tool handler which fetches user details from the n8n API.
      // ============ Get User ============
      server.registerTool(
        'n8n_get_user',
        {
          title: 'Get n8n User',
          description: `Get details of a specific user.
    
    Args:
      - id (string): User ID
    
    Returns:
      User details with id, email, name, and role.`,
          inputSchema: IdParamSchema,
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
          }
        },
        async (params: z.infer<typeof IdParamSchema>) => {
          const user = await get<N8nUser>(`/users/${params.id}`);
          
          return {
            content: [{ type: 'text', text: formatUser(user) }],
            structuredContent: user
          };
        }
      );
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and idempotentHint=true, covering safety and idempotency. The description adds minimal behavioral context by specifying the return fields (id, email, name, role), but doesn't disclose additional traits like error conditions, authentication needs, or rate limits. It doesn't contradict annotations, so a baseline 3 is appropriate given the annotation coverage.

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 appropriately sized and front-loaded with the main purpose in the first sentence. The Args and Returns sections are structured but could be more integrated; however, they add value without waste. It's efficient but not perfectly streamlined.

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 (single parameter, read-only operation) and rich annotations, the description is mostly complete. It specifies return fields, which compensates for the lack of an output schema. However, it could improve by clarifying usage relative to siblings. For a simple getter tool, it's adequate but not exhaustive.

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%, with the parameter 'id' fully documented in the schema as 'The unique identifier of the resource.' The description adds no additional meaning beyond stating 'User ID' in the Args section, which is redundant. Baseline 3 is correct when the schema does the heavy lifting.

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: 'Get details of a specific user.' It uses a specific verb ('Get') and resource ('user'), but doesn't explicitly differentiate from sibling tools like 'n8n_get_current_user' or 'n8n_list_users', which would require a 5. The description is accurate and not tautological.

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. It doesn't mention sibling tools like 'n8n_get_current_user' (for the authenticated user) or 'n8n_list_users' (for multiple users), nor does it specify prerequisites or exclusions. Usage is implied but not explicitly stated.

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