Skip to main content
Glama

n8n_add_user_to_project

Assign a user to a project with a specific role to manage access and permissions within n8n workflows.

Instructions

Add a user to a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID
userIdYesUser ID
roleYesUser role in project

Implementation Reference

  • The handler case that processes the 'n8n_add_user_to_project' tool, performs input validation, and calls the N8nClient.
    case 'n8n_add_user_to_project': {
      if (!args?.projectId || !args?.userId || !args?.role) {
        throw new Error('projectId, userId, and role are required');
      }
      const result = await n8nClient.addUserToProject(args.projectId as string, args.userId as string, args.role as string);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The underlying API client method that makes the POST request to add a user to a project in n8n.
    async addUserToProject(projectId: string, userId: string, role: string): Promise<any> {
      const response = await this.client.post(`/projects/${projectId}/users`, { userId, role });
      return response.data;
    }
  • src/index.ts:864-874 (registration)
    The registration definition for the 'n8n_add_user_to_project' tool, including its schema and description.
    name: 'n8n_add_user_to_project',
    description: 'Add a user to a project',
    inputSchema: {
      type: 'object',
      properties: {
        projectId: { type: 'string', description: 'Project ID' },
        userId: { type: 'string', description: 'User ID' },
        role: { type: 'string', description: 'User role in project' },
      },
      required: ['projectId', 'userId', 'role'],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but discloses almost nothing: no mention of idempotency (what if user already exists?), error conditions, permission requirements, or whether this overwrites existing roles. 'Add' implies mutation but lacks critical behavioral context.

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?

Extremely concise at 5 words, but underspecified rather than efficiently informative. It front-loads the action but wastes no space because it provides essentially no information beyond the function 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?

Incomplete for a mutation tool with 3 parameters and no output schema. Lacks clarification on relationship to update/remove siblings, success return values, or error handling patterns that would help the agent use the tool correctly.

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?

Input schema has 100% description coverage (projectId, userId, role all documented), establishing a baseline of 3. The description adds no additional semantic value such as valid role values, ID formats, or examples, but does not need to compensate for schema gaps.

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 (add) and resource (user to project) clearly, but fails to distinguish from sibling tools like n8n_update_user_in_project or n8n_remove_user_from_project. It does not clarify whether this creates a new membership or modifies existing ones.

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_update_user_in_project, prerequisites (whether user/project must exist first), or expected outcomes. The agent receives no hints about appropriate calling context.

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