Skip to main content
Glama

n8n_update_user_role

Modify user permissions in n8n by changing their assigned role. Specify the user ID and new role to update access levels for workflow management and administrative tasks.

Instructions

Update a user's role

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUser ID
roleYesNew role

Implementation Reference

  • The actual API call to n8n to update a user's role.
    async updateUserRole(id: string, role: string): Promise<any> {
      const response = await this.client.patch(`/users/${id}/role`, { role });
      return response.data;
    }
  • src/index.ts:806-817 (registration)
    The MCP tool definition (schema and metadata) for n8n_update_user_role.
    {
      name: 'n8n_update_user_role',
      description: 'Update a user\'s role',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'User ID' },
          role: { type: 'string', description: 'New role' },
        },
        required: ['id', 'role'],
      },
    },
  • The MCP tool handler in index.ts that processes the request and calls the n8nClient method.
    case 'n8n_update_user_role': {
      if (!args?.id || !args?.role) throw new Error('id and role are required');
      const result = await n8nClient.updateUserRole(args.id as string, args.role as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It fails to mention what role values are valid, whether the change is immediate, if it affects active sessions, or what permissions are required to execute this mutation.

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 extremely brief (4 words), the conciseness is not a virtue here because critical behavioral and contextual information is missing. The description is front-loaded with the verb but lacks the supporting detail needed for a safe mutation operation.

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?

As a mutation tool with no annotations and no output schema, the description should disclose safety characteristics and side effects. It lacks information about valid role enumerations, irreversible actions, or the relationship to project-level role updates, making it incomplete.

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 coverage is 100% with 'User ID' and 'New role' already defined. The description adds minimal semantic value beyond the schema, merely confirming the operation type implied by the parameter names. Baseline 3 applies since schema does the heavy lifting.

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 action (update) and target resource (user's role) clearly, but lands at 'vague' rather than specific. It fails to distinguish from sibling tool 'n8n_update_user_in_project', leaving ambiguity about whether this updates global roles or project-specific roles.

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 tool versus alternatives like n8n_update_user_in_project or n8n_create_user. No prerequisites, permission requirements, or workflow context is 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