Skip to main content
Glama

n8n_create_user

Add new users to n8n by providing email, name, and role details for workflow management and administrative access.

Instructions

Create a new user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesUser email
firstNameNoFirst name
lastNameNoLast name
roleNoUser role

Implementation Reference

  • The actual API call implementation for creating a user in n8n.
    async createUser(data: any): Promise<any> {
      const response = await this.client.post('/users', data);
      return response.data;
    }
  • src/index.ts:300-306 (registration)
    The tool handler registration/logic switch case.
    case 'n8n_create_user': {
      if (!args?.email) throw new Error('email is required');
      const result = await n8nClient.createUser(args);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The schema definition for the n8n_create_user tool.
    name: 'n8n_create_user',
    description: 'Create a new user',
    inputSchema: {
      type: 'object',
      properties: {
        email: { type: 'string', description: 'User email' },
        firstName: { type: 'string', description: 'First name' },
        lastName: { type: 'string', description: 'Last name' },
        role: { type: 'string', description: 'User role' },
      },
      required: ['email'],
    },
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 but fails to mention side effects, idempotency behavior, required permissions, or error scenarios (e.g., duplicate email handling).

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 concise at four words with no wasted text. However, the single sentence fails to earn its place by providing minimal value beyond the tool name itself.

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?

For a creation tool with no annotations and no output schema, the description is inadequate. It omits critical context such as the relationship between user creation and project assignment (n8n_add_user_to_project), hierarchical user management in n8n, or confirmation of what gets returned upon success.

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 baseline score applies. The description adds no parameter-specific context (e.g., valid email formats, available roles, default values), but the schema adequately documents the four fields.

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

Purpose2/5

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

The description 'Create a new user' is tautological, simply converting the snake_case name 'n8n_create_user' into a sentence. While it identifies the verb and resource, it does not clarify what type of user (instance-level vs project-member) or distinguish from siblings like n8n_add_user_to_project.

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 versus alternatives like n8n_add_user_to_project (adding existing users vs creating new ones), prerequisites for creation, or what happens if the email already exists.

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