delete_tag
Remove a tag from n8n workflows using its ID. Clean up your workflow organization by deleting unwanted tags.
Instructions
Delete a tag by ID
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Remove a tag from n8n workflows using its ID. Clean up your workflow organization by deleting unwanted tags.
Delete a tag by ID
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description only says 'Delete', which implies removal, but lacks any disclosure about permanence, associated resource effects, permissions needed, or response behavior. Without annotations, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short (one sentence) with no fluff, but it is too brief at the expense of essential details. Conciseness is good, but not at the cost of completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of output schema and annotations, the description is incomplete. An agent lacks information on deletion behavior, error handling, or prerequisite checks, making it inadequate for safe use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% coverage and the only parameter 'id' is not elaborated. The description adds no meaning beyond 'by ID', failing to clarify format, constraints, or how to obtain the ID.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Delete a tag by ID', specifying the action (delete), the resource (tag), and the identifier (by ID), which distinguishes it from sibling tools like create_tag or update_tag.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, such as deactivate_tag or update_tag, nor are there any prerequisites or when-not-to-use instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/get2knowio/n8n-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server