Skip to main content
Glama

Delete tag

n8n_delete_tag

Delete a tag by ID while preserving its association with workflows.

Instructions

Delete a tag by ID. This does not affect workflows that used this tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagIdYesTag ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
Behavior3/5

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

With no annotations, the description carries the burden. It reveals one key behavioral trait: 'does not affect workflows that used this tag.' However, it omits other traits like irreversibility or permission requirements.

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?

Two sentences, no wasted words. Concise but could be slightly more informative without losing efficiency.

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?

For a simple delete tool with output schema, the description covers the essential behavioral note. Adequately complete given the tool's complexity.

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 coverage is 100%, so baseline is 3. The description repeats 'by ID' but adds no additional meaning beyond the schema's 'Tag ID'.

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?

Clearly states 'Delete a tag by ID' and adds a behavioral note that it doesn't affect workflows. Specific verb and resource, but no explicit sibling differentiation.

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 on when to use this tool vs alternatives like n8n_update_tag or n8n_create_tag. Absence of annotations places burden on description, which only states the basic action.

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

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