Skip to main content
Glama

n8n_get_user

Retrieve user details by ID to manage access, permissions, and administrative tasks in n8n workflows.

Instructions

Get a specific user by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUser ID

Implementation Reference

  • The actual implementation of getUser which calls the n8n API.
    async getUser(id: string): Promise<any> {
      const response = await this.client.get(`/users/${id}`);
      return response.data;
    }
  • MCP tool handler for n8n_get_user.
    case 'n8n_get_user': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.getUser(args.id as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • Registration and schema definition for n8n_get_user tool.
    {
      name: 'n8n_get_user',
      description: 'Get a specific user by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'User ID' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description does not confirm safety characteristics, disclose what happens if the ID is not found, describe the return format, or mention rate limits.

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

Conciseness5/5

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

The description is a single, efficient sentence of six words that is appropriately front-loaded with the verb. There is no redundant or wasteful text for this simple single-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one required parameter, no output schema, basic CRUD operation), the description provides minimal viable information. However, it lacks behavioral context like error handling for missing IDs or expected return structure, which would be necessary for a complete specification without an output schema.

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?

The input schema has 100% description coverage (the 'id' parameter is described as 'User ID'). The description references 'by ID', creating a semantic link to the parameter, but does not add syntax details, format constraints, or examples beyond what the schema already provides. Baseline 3 is appropriate for high-coverage schemas.

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 uses a specific verb ('Get') and resource ('user') and qualifies it with 'specific' and 'by ID', implicitly distinguishing it from the sibling tool n8n_list_users. However, it does not explicitly name the sibling alternative or clarify when to prefer listing over getting.

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 explicit guidance on when to use this tool versus alternatives (e.g., n8n_list_users), nor does it mention prerequisites such as permissions or authentication requirements. There are no 'when-not' exclusions or conditions mentioned.

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