Skip to main content
Glama

n8n_remove_user_from_project

Remove a user from an n8n project by specifying the project ID and user ID to manage access permissions.

Instructions

Remove a user from a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID
userIdYesUser ID

Implementation Reference

  • The implementation of removeUserFromProject in the n8n client.
    async removeUserFromProject(projectId: string, userId: string): Promise<any> {
      const response = await this.client.delete(`/projects/${projectId}/users/${userId}`);
      return response.data;
    }
  • The tool handler in src/index.ts that invokes n8nClient.removeUserFromProject.
    case 'n8n_remove_user_from_project': {
      if (!args?.projectId || !args?.userId) {
        throw new Error('projectId and userId are required');
      }
      const result = await n8nClient.removeUserFromProject(args.projectId as string, args.userId as string);
      return {
        content: [{ type: 'text', text: `User removed from project successfully` }],
      };
    }
  • Tool registration and input schema definition for n8n_remove_user_from_project.
    {
      name: 'n8n_remove_user_from_project',
      description: 'Remove a user from a project',
      inputSchema: {
        type: 'object',
        properties: {
          projectId: { type: 'string', description: 'Project ID' },
          userId: { type: 'string', description: 'User ID' },
        },
        required: ['projectId', 'userId'],
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 disclosure but only states the action verb 'Remove'. It fails to mention whether this is reversible, what happens to the user's workflows/credentials within the project, or required permissions (admin vs self-removal).

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?

The single sentence is efficient and front-loaded with no wasted words. However, extreme brevity contributes to under-specification for a 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?

For a user management mutation with no output schema and no annotations, the description is insufficient. It lacks critical safety context: side effects on project resources, reversibility, or whether the operation cascades to owned workflows.

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 ('Project ID', 'User ID'), establishing a baseline of 3. The tool description adds no additional semantic context about parameter formats, constraints, or relationships beyond what the schema provides.

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 action (remove) and scope (user from project) but is essentially a sentence-case expansion of the tool name 'n8n_remove_user_from_project'. While it implicitly distinguishes from 'n8n_delete_user' (removal vs deletion), it lacks specificity about what 'project' means in the n8n context or any behavioral details.

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 siblings like 'n8n_update_user_in_project' (role change) or 'n8n_delete_user' (global deletion). No mention of prerequisites such as the user needing existing project membership.

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