Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

Update n8n Project

n8n_update_project
Idempotent

Rename an n8n project by providing its ID and new name to update workflow organization.

Instructions

Rename a project.

Args:

  • id (string): Project ID to update

  • name (string): New project name

Returns: The updated project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject ID to update
nameYesNew project name

Implementation Reference

  • The tool definition and handler for 'n8n_update_project', which uses a 'put' request to update a project.
      server.registerTool(
        'n8n_update_project',
        {
          title: 'Update n8n Project',
          description: `Rename a project.
    
    Args:
      - id (string): Project ID to update
      - name (string): New project name
    
    Returns:
      The updated project.`,
          inputSchema: UpdateProjectSchema,
          annotations: {
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
          }
        },
        async (params: z.infer<typeof UpdateProjectSchema>) => {
          const { id, ...updateData } = params;
          const project = await put<N8nProject>(`/projects/${id}`, updateData);
          
          return {
            content: [{ type: 'text', text: `✅ Project updated!\n\n${formatProject(project)}` }],
            structuredContent: project
          };
        }
      );
  • Registration of the 'n8n_update_project' tool within the MCP server.
      server.registerTool(
        'n8n_update_project',
        {
          title: 'Update n8n Project',
          description: `Rename a project.
    
    Args:
      - id (string): Project ID to update
      - name (string): New project name
    
    Returns:
      The updated project.`,
          inputSchema: UpdateProjectSchema,
          annotations: {
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: false
          }
        },
        async (params: z.infer<typeof UpdateProjectSchema>) => {
          const { id, ...updateData } = params;
          const project = await put<N8nProject>(`/projects/${id}`, updateData);
          
          return {
            content: [{ type: 'text', text: `✅ Project updated!\n\n${formatProject(project)}` }],
            structuredContent: project
          };
        }
      );
Behavior3/5

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

Annotations provide key behavioral hints: readOnlyHint=false (mutation), idempotentHint=true (safe to retry), destructiveHint=false (non-destructive). The description adds that it 'renames' a project, which clarifies the specific type of update beyond the generic title. However, it doesn't disclose additional context like authentication needs, rate limits, or what happens to other project attributes during rename. No contradiction with annotations exists.

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 and front-loaded with the core purpose ('Rename a project.'). The Args and Returns sections are structured but somewhat redundant given the schema. Every sentence serves a purpose, though the parameter descriptions could be omitted without loss since they duplicate the schema.

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 mutation tool with 2 parameters, 100% schema coverage, and annotations covering safety (idempotent, non-destructive), the description is minimally adequate. It lacks an output schema, so the 'Returns' statement is helpful but vague ('The updated project'). More detail on the return structure or error conditions would improve completeness, but annotations provide critical behavioral context.

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?

Schema description coverage is 100%, with both parameters ('id' and 'name') fully documented in the schema. The description repeats the parameter purposes in the 'Args' section but adds no extra meaning beyond what the schema already provides (e.g., no examples, constraints like name uniqueness, or format details). This meets the baseline for high 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 tool's purpose with 'Rename a project' - a specific verb (rename) and resource (project). It distinguishes from siblings like 'n8n_create_project' (creation) and 'n8n_delete_project' (deletion), though it doesn't explicitly contrast with 'n8n_update_workflow' or other update tools. The title 'Update n8n Project' is slightly broader than the description's focus on renaming.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing project ID), when not to use it, or how it differs from other update tools like 'n8n_update_workflow' or 'n8n_update_variable'. The agent must infer usage from the tool name and sibling list alone.

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

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