Delete Flow
node-red-flows-deleteDelete a flow tab from Node-RED by providing its unique identifier.
Instructions
Delete a flow tab from Node-RED
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
node-red-flows-deleteDelete a flow tab from Node-RED by providing its unique identifier.
Delete a flow tab from Node-RED
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description fails to disclose any behavioral traits beyond the action. No indication of side effects, permissions, or whether the action is reversible.
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 a single, direct sentence with no wasted words, appropriate for a simple delete operation.
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?
Missing critical context: no indication of return values, side effects, or confirmation requirements. For a delete operation, more details are expected.
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?
Schema coverage is 0% and the description adds no meaning for the 'id' parameter beyond its existence. The value's nature (e.g., flow tab identifier) is not explained.
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 the action ('Delete') and resource ('a flow tab from Node-RED'), distinguishing it from sibling tools like node-red-flows-list or node-red-flows-get.
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?
The description provides no guidance on when to use this tool, prerequisites, or alternatives. No mention of permanent deletion or recovery options.
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/kskwon02/node-red-ai-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server