Skip to main content
Glama
DrBalls

n8n MCP Server

by DrBalls

Create n8n Tag

n8n_create_tag

Create a new tag to organize and categorize workflows in n8n for better management and retrieval.

Instructions

Create a new tag for organizing workflows.

Args:

  • name (string): Tag name (max 24 characters)

Returns: The created tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTag name (max 24 characters)

Implementation Reference

  • The handler logic that executes the 'n8n_create_tag' tool.
      async (params: z.infer<typeof CreateTagSchema>) => {
        const tag = await post<N8nTag>('/tags', params);
        
        return {
          content: [{ type: 'text', text: `✅ Tag created!\n\n${formatTag(tag)}` }],
          structuredContent: tag
        };
      }
    );
  • The registration block for the 'n8n_create_tag' tool.
      server.registerTool(
        'n8n_create_tag',
        {
          title: 'Create n8n Tag',
          description: `Create a new tag for organizing workflows.
    
    Args:
      - name (string): Tag name (max 24 characters)
    
    Returns:
      The created tag.`,
          inputSchema: CreateTagSchema,
          annotations: {
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: false,
            openWorldHint: false
          }
        },
        async (params: z.infer<typeof CreateTagSchema>) => {
          const tag = await post<N8nTag>('/tags', params);
          
          return {
            content: [{ type: 'text', text: `✅ Tag created!\n\n${formatTag(tag)}` }],
            structuredContent: tag
          };
        }
      );
Behavior3/5

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

Annotations indicate this is a non-readOnly, non-destructive, non-idempotent, non-openWorld operation, which the description aligns with by implying creation (not reading or deleting). The description adds minimal behavioral context beyond annotations—it mentions the tag's purpose ('organizing workflows') but doesn't cover permissions, rate limits, or what happens on duplicate names. 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 front-loaded with the core purpose in the first sentence, followed by structured 'Args' and 'Returns' sections. It avoids redundancy, but the 'Args' section slightly repeats schema information without adding value, preventing a perfect score.

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?

Given the tool's simplicity (1 parameter, 100% schema coverage, no output schema), the description is adequate but minimal. It explains what the tool does and the return value ('The created tag'), but lacks details on error cases, idempotency, or integration with other tools (e.g., how tags relate to workflows), leaving some contextual gaps.

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 description briefly mentions the 'name' parameter and its constraint ('max 24 characters'), but the input schema already provides full coverage (100%) with identical details. No additional semantic context is added, such as naming conventions or uniqueness requirements, keeping it at 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 action ('Create a new tag') and purpose ('for organizing workflows'), making the tool's function immediately understandable. It distinguishes from siblings like 'n8n_update_tag' and 'n8n_delete_tag' by specifying creation rather than modification or deletion. However, it doesn't explicitly contrast with 'n8n_get_tag' or 'n8n_list_tags' for read 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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing existing workflows to tag), when not to use it (e.g., if a tag already exists), or how it relates to sibling tools like 'n8n_update_workflow_tags' for applying tags to workflows.

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