Skip to main content
Glama

n8n_delete_project

Remove a project from n8n by specifying its ID to manage workflow organization and clean up unused resources.

Instructions

Delete a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject ID to delete

Implementation Reference

  • MCP tool handler that calls n8nClient.deleteProject.
    case 'n8n_delete_project': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.deleteProject(args.id as string);
      return {
        content: [{ type: 'text', text: `Project ${args.id as string} deleted successfully` }],
      };
    }
  • Implementation of the n8n API call to delete a project.
    async deleteProject(id: string): Promise<any> {
      const response = await this.client.delete(`/projects/${id}`);
      return response.data;
  • src/index.ts:852-862 (registration)
    Tool registration for n8n_delete_project.
    {
      name: 'n8n_delete_project',
      description: 'Delete a project',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Project ID to delete' },
        },
        required: ['id'],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to state whether deletion is permanent or reversible, whether it cascades to contained resources (workflows, credentials), or what permissions are required. Only the basic action type is implied by the verb.

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?

The description is extremely brief (3 words) with no structural organization possible at this length. While there is no wasted text, the extreme under-specification means it fails to earn a higher score - conciseness requires informative density, not just brevity.

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 single-parameter tool with no output schema and no annotations, the description should explain irreversibility, success/failure behavior, and side effects. It provides none of these, making it dangerously incomplete for an agent deciding whether to invoke a destructive operation.

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?

With 100% schema description coverage ('Project ID to delete'), the baseline score applies. The description adds no semantic context about the ID format, how to obtain it, or validation rules, but the schema adequately documents the single parameter.

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 project' is tautological - it simply restates the tool name (n8n_delete_project). While it identifies the verb and resource, it fails to distinguish from sibling delete operations (n8n_delete_workflow, n8n_delete_user, etc.) or specify what constitutes a 'project' in this context.

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 tool versus alternatives, prerequisites (such as emptying the project first), or permission requirements. For a destructive operation, the absence of usage constraints or warnings 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/Shravan1610/n8n-mcp-server'

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