Skip to main content
Glama

n8n_delete_tag

Remove a tag from n8n workflows by specifying its ID to maintain organized automation processes.

Instructions

Delete a tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTag ID to delete

Implementation Reference

  • Actual implementation of deleting a tag in n8n-client.
    async deleteTag(id: string): Promise<any> {
      const response = await this.client.delete(`/tags/${id}`);
      return response.data;
    }
  • Tool handler for 'n8n_delete_tag' that invokes the n8n client.
    case 'n8n_delete_tag': {
      if (!args?.id) throw new Error('id is required');
      const result = await n8nClient.deleteTag(args.id as string);
      return {
        content: [{ type: 'text', text: `Tag ${args.id as string} deleted successfully` }],
      };
    }
  • src/index.ts:750-760 (registration)
    Tool registration definition for 'n8n_delete_tag'.
    {
      name: 'n8n_delete_tag',
      description: 'Delete a tag',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Tag ID to delete' },
        },
        required: ['id'],
      },
    },
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 behavioral disclosure burden, yet it provides no information about permanence, side effects on workflows using this tag, or error handling. The agent cannot determine if this is a hard delete or soft delete, or what happens to associated workflow relationships.

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 extremely brief at three words. While it wastes no words and is front-loaded by default, the brevity contributes to under-specification rather than clarity. However, given the constraint that every sentence must earn its place, the single statement is appropriately efficient.

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 destructive operation with no annotations and no output schema, the description is inadequate. It fails to disclose critical context such as deletion permanence, cascading effects on workflows (given sibling n8n_update_workflow_tags exists), or success/failure indicators that an agent would need to safely invoke this tool.

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 (the 'id' parameter is fully described in the schema), the baseline score is 3. The description adds no additional parameter semantics (e.g., format details, where to obtain the ID), but none are required given the complete schema coverage.

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?

The description 'Delete a tag' is tautological, restating the function name (n8n_delete_tag) without adding specificity. It does not distinguish this from sibling operations like n8n_update_tag or n8n_create_tag, nor does it clarify what 'tag' refers to in the n8n context.

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 usage guidance is provided. The description does not indicate when to use delete versus update_tag, whether deletion is permanent, or if workflows must be untagged first (prerequisites). There are no alternatives or exclusions mentioned despite numerous sibling tag management tools.

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