Skip to main content
Glama

n8n_create_tag

Create new tags in n8n to organize and categorize workflows for better management and filtering.

Instructions

Create a new tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTag name

Implementation Reference

  • The tool handler in src/index.ts that receives the request and delegates to the n8nClient.
    case 'n8n_create_tag': {
      if (!args?.name) throw new Error('name is required');
      const result = await n8nClient.createTag(args as any);
      return {
        content: [{ type: 'text', text: formatResponse(result) }],
      };
    }
  • The implementation of the 'createTag' method in the N8nClient class.
    async createTag(data: { name: string }): Promise<any> {
      const response = await this.client.post('/tags', data);
      return response.data;
    }
  • src/index.ts:716-726 (registration)
    Tool registration in src/index.ts, defining the schema and name.
    {
      name: 'n8n_create_tag',
      description: 'Create a new tag',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Tag name' },
        },
        required: ['name'],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It fails to specify idempotency behavior, what the operation returns (no output schema exists), or side effects beyond the basic creation act.

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 single sentence is appropriately sized and front-loaded with the action. While underspecified for completeness, the structure itself is efficient with no wasted words.

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 mutation tool with no output schema and no annotations, the description is insufficient. It omits the tag's purpose (workflows vs. projects), return structure, and error handling, leaving critical gaps despite the low parameter complexity.

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 for the single 'name' parameter, the baseline is 3. The description adds no additional semantic context about naming constraints, permitted characters, or maximum length beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the basic verb and resource ('Create a new tag'), which is clear but minimal. It fails to specify the domain (n8n workflow tags) or distinguish from siblings like n8n_update_tag beyond the verb choice, leaving scope ambiguous.

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_update_tag or n8n_update_workflow_tags, nor does it mention prerequisites (e.g., whether tag names must be unique) or error conditions for duplicates.

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