Skip to main content
Glama

n8n_create_project

Create a new project in n8n by specifying a name and optional type to organize workflows and automation tasks.

Instructions

Create a new project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
typeNoProject type

Implementation Reference

  • The actual implementation of the project creation in the n8n API client.
    async createProject(data: { name: string; type?: string }): Promise<any> {
      const response = await this.client.post('/projects', data);
      return response.data;
    }
  • The tool handler that receives the request and calls the n8n client.
    case 'n8n_create_project': {
      if (!args?.name) throw new Error('name is required');
      const result = await n8nClient.createProject(args as any);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • src/index.ts:827-838 (registration)
    The tool registration defining the schema and input requirements for 'n8n_create_project'.
    {
      name: 'n8n_create_project',
      description: 'Create a new project',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Project name' },
          type: { type: 'string', description: 'Project type' },
        },
        required: ['name'],
      },
    },
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 but offers almost nothing. It does not specify side effects (e.g., default permissions set), idempotency behavior on name conflicts, or what fields are initialized beyond the name parameter.

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 at four words, avoiding verbosity, but it is under-specified rather than efficiently concise. The single sentence does not earn its place effectively given the lack of substance, though it is grammatically complete.

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 creation tool with no output schema and no annotations, the description is insufficient. It fails to explain what constitutes a project in n8n, the relationship between projects and users (given the sibling 'n8n_add_user_to_project'), or the implications of the optional 'type' parameter.

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 name' and 'Project type'), the schema adequately documents both parameters. The description adds no additional semantic context (e.g., valid values for 'type', naming constraints), meeting the baseline expectation when structured documentation is already complete.

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 'Create a new project' is tautological, restating the action and resource already present in the tool name 'n8n_create_project' with only the addition of 'new'. It fails to distinguish what an n8n project specifically is or how it differs from workflows, credentials, or other sibling resources.

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 like 'n8n_update_project' for modifications or prerequisites such as user permissions. There are no exclusions or contextual conditions provided.

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