delete_note
Delete a specific sticky note from a workflow by providing its unique note identifier.
Instructions
Delete sticky note
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note_id | Yes |
Delete a specific sticky note from a workflow by providing its unique note identifier.
Delete sticky note
| Name | Required | Description | Default |
|---|---|---|---|
| note_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations and only the word 'Delete', the description does not disclose whether deletion is irreversible, requires permissions, or affects related data.
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 extremely short at two words, which is concise but omits necessary details; it does not fully earn its place.
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 single parameter, no output schema, and no annotations, the description lacks essential behavioral details such as return values or error conditions.
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 sole parameter `note_id` has no description in the schema, and the tool description adds no meaning about its format or purpose, failing to compensate for 0% schema coverage.
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 the resource 'sticky note', distinguishing it from sibling tools like add_note, edit_note, and list_notes.
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 on when to use this tool versus alternatives like delete_node, or what prerequisites are needed (e.g., note must exist).
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/Pulse-Intelligence/pulse-workflow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server