Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

delete_tag

Delete a tag by its ID to remove it from workflow organization in n8n.

Instructions

Delete a tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagIdYesThe ID of the tag to delete

Implementation Reference

  • Handler for the 'delete_tag' tool. Parses tagId from args using TagIdSchema, then calls client.deleteTag(tagId).
    case "delete_tag": {
      const { tagId } = TagIdSchema.parse(args);
      return await client.deleteTag(tagId);
    }
  • Zod schema for delete_tag input validation: requires a 'tagId' string.
    const TagIdSchema = z.object({
      tagId: z.string(),
    });
  • src/tools.ts:291-304 (registration)
    Tool registration definition for delete_tag with name, description, and inputSchema (requires tagId).
    {
      name: "delete_tag",
      description: "Delete a tag",
      inputSchema: {
        type: "object",
        properties: {
          tagId: {
            type: "string",
            description: "The ID of the tag to delete",
          },
        },
        required: ["tagId"],
      },
    },
  • Actual API call implementation: sends DELETE /api/v1/tags/{id} via axios and returns a success message.
    async deleteTag(id: string) {
      await this.client.delete(`/api/v1/tags/${id}`);
      return { success: true, message: `Tag ${id} deleted successfully` };
    }
Behavior2/5

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

No annotations exist, so the description must fully disclose behavioral traits. It only states 'Delete a tag' without explaining irreversibility, required permissions, or impact on associated entities like workflows.

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

Conciseness2/5

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

The description is extremely brief but lacks substance. While concise, it does not earn its place because it adds no value over the tool name and fails to provide necessary context.

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 simplicity of the tool and lack of output schema, the description is incomplete. It does not address deletion consequences, which is critical for an agent to correctly assess impact.

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 description coverage is 100%, with the parameter 'tagId' already well-documented in the schema. The description adds no extra semantic meaning beyond what the schema provides, meeting the baseline of 3.

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

Purpose1/5

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

Description 'Delete a tag' is a tautology that merely restates the tool name 'delete_tag'. It fails to provide any additional context about the specific resource or distinguish it from sibling tools like 'update_tag' or 'create_tag'.

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 (e.g., 'update_tag' for modifying, or 'get_tags' for listing). There is no mention of prerequisites, side effects, or recommended context.

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/nikolausm/n8n-mcp-server'

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