Skip to main content
Glama

delete-user

Remove a user from your n8n instance by providing their client ID and email or user ID. This tool helps manage user access and maintain security.

Instructions

Delete a user from your instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientIdYes
idOrEmailYes

Implementation Reference

  • Handler function that executes the delete-user tool by retrieving the N8nClient instance and invoking its deleteUser method with the provided idOrEmail.
    case "delete-user": {
      const { clientId, idOrEmail } = args as { clientId: string; idOrEmail: string };
      const client = clients.get(clientId);
      if (!client) {
        return {
          content: [{
            type: "text",
            text: "Client not initialized. Please run init-n8n first.",
          }],
          isError: true
        };
      }
    
      try {
        await client.deleteUser(idOrEmail);
        return {
          content: [{
            type: "text",
            text: `Successfully deleted user: ${idOrEmail}`,
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: error instanceof Error ? error.message : "Unknown error occurred",
          }],
          isError: true
        };
      }
    }
  • src/index.ts:603-614 (registration)
    Registration of the 'delete-user' tool in the ListToolsRequestSchema response, specifying name, description, and input schema.
    {
      name: "delete-user",
      description: "Delete a user from your instance.",
      inputSchema: {
        type: "object",
        properties: {
          clientId: { type: "string" },
          idOrEmail: { type: "string" }
        },
        required: ["clientId", "idOrEmail"]
      }
    },
  • Helper method in N8nClient class that sends the DELETE request to the n8n API endpoint /users/{idOrEmail} to delete the user.
    async deleteUser(idOrEmail: string): Promise<void> {
      return this.makeRequest<void>(`/users/${idOrEmail}`, {
        method: 'DELETE',
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify consequences (e.g., data loss, irreversibility), permissions required, rate limits, or what happens to associated resources. For a destructive operation with zero annotation coverage, this is inadequate.

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?

The description is a single, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse. Every word earns its place without being overly terse.

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?

Given the tool's destructive nature, 2 required parameters with 0% schema coverage, no annotations, and no output schema, the description is insufficient. It should address risks, parameter meanings, and expected outcomes. The conciseness comes at the cost of completeness for a high-stakes operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning neither parameter (clientId, idOrEmail) is documented in the schema. The description adds no information about these parameters—it doesn't explain what clientId refers to, whether idOrEmail accepts user IDs or email addresses, or their format. With 2 required parameters and no schema documentation, the description fails to compensate.

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 clearly states the action ('Delete') and the target resource ('a user from your instance'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other deletion tools like delete-credential, delete-project, or delete-workflow, which would require specifying what distinguishes user deletion from other resource deletions.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., user must exist), exclusions (e.g., cannot delete active users), or related tools like get-user for verification or create-users for reversal. With multiple sibling deletion tools, this lack of differentiation is a significant gap.

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/illuminaresolutions/n8n-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server