Skip to main content
Glama

n8n_update_user_in_project

Modify user permissions by changing their role within a specific n8n project to control access and responsibilities.

Instructions

Update a user's role in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID
userIdYesUser ID
roleYesNew role

Implementation Reference

  • The tool handler case that calls the n8n client method.
    case 'n8n_update_user_in_project': {
      if (!args?.projectId || !args?.userId || !args?.role) {
        throw new Error('projectId, userId, and role are required');
      }
      const result = await n8nClient.updateUserInProject(args.projectId as string, args.userId as string, args.role as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The implementation of the updateUserInProject method in the N8nClient class.
    async updateUserInProject(projectId: string, userId: string, role: string): Promise<any> {
      const response = await this.client.patch(`/projects/${projectId}/users/${userId}`, { role });
      return response.data;
    }
  • src/index.ts:888-900 (registration)
    The tool definition and schema registration for n8n_update_user_in_project.
    {
      name: 'n8n_update_user_in_project',
      description: 'Update a user\'s role in a project',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'Project ID' },
          userId: { type: 'string', description: 'User ID' },
          role: { type: 'string', description: 'New role' },
        },
        required: ['projectId', 'userId', 'role'],
      },
    },
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. It only states the basic mutation action without disclosing idempotency, what happens if the user isn't in the project, valid role values, or permission requirements.

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?

Seven words with no redundancy. The single sentence front-loads the action and scope efficiently—every word earns its place.

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?

Adequate for identifying the operation, but given no output schema and no annotations, the description should specify valid role values and prerequisites (user must exist in project). It meets minimum viability but leaves operational gaps.

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 clear labels ('Project ID', 'User ID', 'New role'), establishing a baseline of 3. The description doesn't add value beyond the schema regarding valid role formats or accepted values, which is critical given the lack of enum constraints.

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 ('Update') with clear resource ('user's role in a project'), distinguishing it from global user management. However, it doesn't explicitly differentiate from the sibling 'n8n_update_user_role' (likely global) vs this project-scoped operation.

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 'n8n_add_user_to_project' (prerequisite: user must already be in project) or 'n8n_remove_user_from_project'. Also lacks guidance on valid role values since the schema lacks enums.

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