Skip to main content
Glama

update-project

Modify a project's name in n8n using the MCP server. Requires n8n Enterprise license with project management features enabled.

Instructions

Update a project's name. 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
nameYes

Implementation Reference

  • Handler function in the CallToolRequestSchema that executes the update-project tool by calling N8nClient.updateProject
    case "update-project": {
      const { clientId, projectId, name } = args as { clientId: string; projectId: string; name: 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.updateProject(projectId, name);
        return {
          content: [{
            type: "text",
            text: `Successfully updated project ${projectId} with new name: ${name}`,
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: error instanceof Error ? error.message : "Unknown error occurred",
          }],
          isError: true
        };
      }
    }
  • Input schema definition for the update-project tool in the tools list returned by ListToolsRequestSchema
      name: "update-project",
      description: "Update a project's name. 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" },
          name: { type: "string" }
        },
        required: ["clientId", "projectId", "name"]
      }
    },
  • src/index.ts:543-554 (registration)
    Registration of the update-project tool within the ListToolsRequestSchema handler's tools array
      name: "update-project",
      description: "Update a project's name. 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" },
          name: { type: "string" }
        },
        required: ["clientId", "projectId", "name"]
      }
    },
  • N8nClient helper method that performs the actual API call to update the project name via PUT request to /projects/{projectId}
    async updateProject(projectId: string, name: string): Promise<void> {
      return this.makeRequest<void>(`/projects/${projectId}`, {
        method: 'PUT',
        body: JSON.stringify({ name }),
      });
    }
Behavior3/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. It adds useful context about licensing requirements and input formatting ('Arguments must be provided as compact, single-line JSON'), but it doesn't cover other behavioral aspects like error handling, response format, or side effects, leaving gaps for a mutation tool.

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 two sentences: the first states the purpose and prerequisites, and the second provides critical formatting instructions. It's front-loaded with essential information, though the formatting note could be integrated more smoothly.

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?

Given the tool's complexity (a mutation with 3 required parameters), no annotations, and no output schema, the description is incomplete. It covers licensing and formatting but misses details on parameters, return values, and potential errors, making it adequate but with clear gaps for effective use.

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?

The schema description coverage is 0%, so the description must compensate for undocumented parameters. It only mentions 'name' as updatable, implying the purpose of that parameter, but doesn't explain 'clientId' or 'projectId' (e.g., their roles in identifying the project). This partial coverage is insufficient given the low schema coverage.

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 verb ('Update') and resource ('a project's name'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'update-workflow' or other update tools, which would be needed for a perfect score.

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 provides explicit context for when to use this tool by stating 'Requires n8n Enterprise license with project management features enabled', which acts as a prerequisite. It doesn't mention alternatives like 'create-project' for new projects or exclusions, so it falls short of a perfect score.

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