Skip to main content
Glama

n8n_create_tag

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

Instructions

Create new tag for workflow categorization. Use meaningful names like "production", "staging", "team-marketing", or "urgent". Tags help filter and organize workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTag name (case-sensitive, spaces allowed)

Implementation Reference

  • The createTag method implements the n8n_create_tag tool logic. It makes a POST request to the n8n API endpoint /tags with the tag name in the request body.
    async createTag(name: string) {
      return this.request(`${this.apiBase}/tags`, {
        method: 'POST',
        body: JSON.stringify({ name }),
      });
    }
  • The tool definition for n8n_create_tag including name, description, inputSchema (requires 'name' parameter), and annotations for MCP tool metadata.
      name: 'n8n_create_tag',
      description: 'Create new tag for workflow categorization. Use meaningful names like "production", "staging", "team-marketing", or "urgent". Tags help filter and organize workflows.',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Tag name (case-sensitive, spaces allowed)' },
        },
        required: ['name'],
      },
      annotations: {
        title: 'Create Tag',
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: false,
        openWorldHint: true,
      },
    },
  • src/server.ts:71-72 (registration)
    The routing case for n8n_create_tag in the handleToolCall function, which delegates to client.createTag(args.name).
    case 'n8n_create_tag':
      return client.createTag(args.name);
  • The N8nTag interface defines the type structure for tags with id, name, createdAt, and updatedAt fields.
    export interface N8nTag {
      id: string;
      name: string;
      createdAt: string;
      updatedAt: string;
    }
Behavior4/5

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

Annotations indicate this is a non-read-only, non-destructive, non-idempotent, open-world operation. The description adds valuable context by explaining the purpose of tags ('help filter and organize workflows'), which is not covered by annotations, though it doesn't detail potential side effects like duplicate handling or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose in the first sentence, followed by actionable guidance and benefits, with no wasted words. Every sentence contributes directly to understanding the tool's use.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter, no output schema) and rich annotations, the description is mostly complete, covering purpose and usage. However, it lacks details on return values or error cases, which would be helpful despite the absence of an output schema.

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 has 100% description coverage, fully documenting the single 'name' parameter. The description adds minimal semantics by suggesting examples like 'production' or 'staging', but does not provide additional details beyond what the schema already states, meeting the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the specific action ('Create new tag') and resource ('for workflow categorization'), distinguishing it from siblings like n8n_update_tag or n8n_delete_tag by focusing on creation rather than modification or deletion.

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?

It provides clear context for when to use the tool (creating tags for organizing workflows) and includes examples of meaningful names, but does not explicitly state when not to use it or name alternatives like n8n_update_tag for modifying existing tags.

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/node2flow-th/n8n-management-mcp-community'

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