Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

update_tag

Update a tag's name by providing its ID and a new name.

Instructions

Update a tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagIdYesThe ID of the tag to update
nameYesNew name for the tag

Implementation Reference

  • src/tools.ts:273-290 (registration)
    Tool registration for 'update_tag' defining its name, description, and input schema (tagId + name, both required).
    {
      name: "update_tag",
      description: "Update a tag",
      inputSchema: {
        type: "object",
        properties: {
          tagId: {
            type: "string",
            description: "The ID of the tag to update",
          },
          name: {
            type: "string",
            description: "New name for the tag",
          },
        },
        required: ["tagId", "name"],
      },
    },
  • Zod validation schema (UpdateTagSchema) defining 'tagId' (string) and 'name' (string) for the update_tag tool.
    const UpdateTagSchema = z.object({
      tagId: z.string(),
      name: z.string(),
    });
  • Handler case for 'update_tag' — parses args with UpdateTagSchema and calls client.updateTag().
    case "update_tag": {
      const { tagId, name } = UpdateTagSchema.parse(args);
      return await client.updateTag(tagId, name);
    }
  • N8nClient.updateTag method — sends PATCH request to /api/v1/tags/{id} with the new name.
    async updateTag(id: string, name: string) {
      const response = await this.client.patch(`/api/v1/tags/${id}`, { name });
      return response.data;
    }
Behavior2/5

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

With no annotations and a bare description, the tool lacks disclosure of behavioral traits like idempotency, error handling (e.g., what happens if tagId is invalid), or side effects. The agent cannot infer key runtime behavior from the description alone.

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 concise at three words, which is efficient but overly minimal. It front-loads the core action but omits necessary detail, making it borderline under-specified rather than optimally concise.

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?

Given the lack of output schema and annotations, the description should cover more contextual information, such as update semantics, constraints, prerequisites, or return values. The current text is insufficient for the agent to fully understand the tool's behavior and results.

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?

The input schema provides descriptions for both parameters (tagId and name) with 100% coverage, so the schema already explains their meaning. The description adds no additional semantics beyond the schema, earning the baseline score of 3.

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 'Update a tag' clearly states the verb (update) and resource (tag), making the basic action unambiguous. However, it does not differentiate from sibling tools like 'create_tag' or 'delete_tag', which also target tags, limiting its usefulness for distinguishing among similar operations.

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 such as 'create_tag' or 'delete_tag'. There is no mention of prerequisites, context, or exclusions, leaving the agent without direction on appropriate usage.

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

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