Skip to main content
Glama

n8n_update_tag

Modify tag names in n8n workflows to maintain organization and reflect changes in your automation processes.

Instructions

Update a tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTag ID
nameYesNew tag name

Implementation Reference

  • The actual implementation of the updateTag method in the n8nClient class.
    async updateTag(id: string, data: { name: string }): Promise<any> {
      const response = await this.client.put(`/tags/${id}`, data);
      return response.data;
  • The request handler for 'n8n_update_tag' which calls the n8nClient.updateTag method.
    case 'n8n_update_tag': {
      if (!args?.id || !args?.name) throw new Error('id and name are required');
      const result = await n8nClient.updateTag(args.id as string, { name: args.name as string });
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The tool registration and schema definition for 'n8n_update_tag'.
    {
      name: 'n8n_update_tag',
      description: 'Update a tag',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Tag ID' },
          name: { type: 'string', description: 'New tag name' },
        },
        required: ['id', 'name'],
      },
    },
Behavior2/5

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

No annotations are present, so description carries full disclosure burden. It states 'Update' implying mutation but doesn't specify whether tags are renamed atomically, if changes cascade to existing workflow associations, or potential failure modes.

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?

Extremely terse at 3 words, but not bloated. Every word earns its place, though the extreme brevity fails to meet the informational needs for tool selection.

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 existence of n8n_update_workflow_tags and other tag siblings, the description lacks domain context needed to select the correct tool. No output schema exists, but even for a simple CRUD tool, the failure to differentiate tag entity updates from tag associations is a critical gap.

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 has 100% description coverage ('Tag ID' and 'New tag name'), so the structured fields already carry the semantic load. Description adds no parameter guidance beyond what's in the schema, warranting baseline score.

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?

Description 'Update a tag' is a tautology that restates the tool name without adding specificity. It fails to distinguish from sibling n8n_update_workflow_tags (which updates tag associations on workflows, not the tag entity itself) or clarify what resource domain 'tag' refers to.

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?

Provides no guidance on when to use this versus n8n_create_tag, n8n_delete_tag, or n8n_update_workflow_tags. Does not mention prerequisites like tag existence or permission requirements.

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