Skip to main content
Glama

delete-project

Remove a project by its ID using client authentication. Requires n8n Enterprise license with project management features enabled. Input must be provided as compact JSON.

Instructions

Delete a project by ID. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientIdYes
projectIdYes

Implementation Reference

  • MCP tool handler for 'delete-project' in the CallToolRequestSchema switch statement. Retrieves the N8nClient instance, validates it exists, calls client.deleteProject(projectId), and returns success or error response.
    case "delete-project": {
      const { clientId, projectId } = args as { clientId: string; projectId: 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.deleteProject(projectId);
        return {
          content: [{
            type: "text",
            text: `Successfully deleted project with ID: ${projectId}`,
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: error instanceof Error ? error.message : "Unknown error occurred",
          }],
          isError: true
        };
      }
    }
  • N8nClient method that performs the actual DELETE request to the n8n API endpoint /projects/{projectId}.
    async deleteProject(projectId: string): Promise<void> {
      return this.makeRequest<void>(`/projects/${projectId}`, {
        method: 'DELETE',
      });
    }
  • src/index.ts:530-541 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the name, description, and input schema for 'delete-project'.
    {
      name: "delete-project",
      description: "Delete a project by ID. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.",
      inputSchema: {
        type: "object",
        properties: {
          clientId: { type: "string" },
          projectId: { type: "string" }
        },
        required: ["clientId", "projectId"]
      }
    },
  • Input schema definition for the 'delete-project' tool, specifying clientId and projectId as required string parameters.
    {
      name: "delete-project",
      description: "Delete a project by ID. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.",
      inputSchema: {
        type: "object",
        properties: {
          clientId: { type: "string" },
          projectId: { type: "string" }
        },
        required: ["clientId", "projectId"]
      }
    },
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It reveals important behavioral traits: the destructive nature (implied by 'Delete'), licensing requirements, and input format constraints. However, it doesn't disclose whether deletion is permanent/reversible, what happens to associated resources, or error conditions.

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 description is appropriately sized with three sentences that each serve distinct purposes: stating the core function, specifying prerequisites, and providing technical constraints. It's front-loaded with the main purpose, though the technical formatting note could potentially be moved to a separate section.

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?

For a destructive operation with no annotations and no output schema, the description provides adequate but incomplete context. It covers licensing requirements and input format, but lacks crucial information about the deletion's permanence, what gets deleted along with the project, and what the response contains. The absence of output schema increases the need for return value explanation.

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?

With 0% schema description coverage and 2 required parameters, the description fails to add meaningful parameter semantics. It mentions 'Arguments must be provided as compact, single-line JSON' but doesn't explain what 'clientId' and 'projectId' represent, their format, or how to obtain them. The description doesn't compensate for the schema's lack of documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Delete') and resource ('project by ID'), distinguishing it from sibling tools like 'delete-workflow', 'delete-user', or 'delete-tag' which target different resources. It provides unambiguous purpose without being tautological.

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

Usage Guidelines4/5

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

The description explicitly states when to use this tool ('Delete a project by ID') and includes important prerequisites ('Requires n8n Enterprise license with project management features enabled'), providing clear context. However, it doesn't specify when NOT to use it or mention alternatives like 'update-project' for modification instead of deletion.

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

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

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