Skip to main content
Glama

n8n_delete_user

Remove a user account from n8n by specifying the user ID. This administrative action permanently deletes user access and data.

Instructions

Delete a user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUser ID to delete

Implementation Reference

  • The core implementation of the delete user operation in the N8nClient class.
    async deleteUser(id: string): Promise<any> {
      const response = await this.client.delete(`/users/${id}`);
      return response.data;
    }
  • The MCP tool handler logic that calls n8nClient.deleteUser.
    case 'n8n_delete_user': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.deleteUser(args.id as string);
      return {
        content: [{ type: 'text', text: `User ${args.id as string} deleted successfully` }],
      };
    }
  • src/index.ts:796-805 (registration)
    The registration of the n8n_delete_user tool, including its input schema definition.
      name: 'n8n_delete_user',
      description: 'Delete a user',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'User ID to delete' },
        },
        required: ['id'],
      },
    },
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. While 'Delete' implies destruction, the description lacks critical safety context: whether the operation is reversible, what happens to the user's workflows/credentials/executions, and required permissions. This is inadequate for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At two words, this is under-specification rather than effective conciseness. The single sentence provides no structural organization of information (e.g., leading with the destructive warning, following with scope).

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 destructive operation with severe consequences (permanent user deletion), the description is dangerously incomplete. No output schema exists, yet the description doesn't compensate by explaining the success/failure behavior or side effects on related resources.

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 the 'id' parameter fully described as 'User ID to delete'. The description adds no semantic value beyond the schema (it doesn't clarify the ID format, where to obtain it, or validation rules), warranting the baseline score for high-coverage schemas.

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 'Delete a user' is a tautology that restates the tool name (n8n_delete_user) without adding specificity. It fails to distinguish from the sibling tool n8n_remove_user_from_project, leaving ambiguity about whether this removes a user's platform account or just their project association.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided for when to use this versus alternatives like n8n_remove_user_from_project or n8n_update_user_role. No prerequisites are mentioned (e.g., whether the user must be deactivated first, or if owned workflows transfer or delete).

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