Skip to main content
Glama
ptamb3

Shortcut MCP Server

by ptamb3

Delete Shortcut Epic

delete_epic

Delete a Shortcut epic permanently by ID. Requires double confirmation to prevent accidental removal.

Instructions

Permanently delete a Shortcut epic by ID. This is IRREVERSIBLE. Requires both confirm='CONFIRM_WRITE' and confirm_delete=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be CONFIRM_WRITE to execute
dry_runNo
epic_idYes
confirm_deleteNoMust be true to confirm permanent deletion
Behavior4/5

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

With no annotations provided, the description carries the full burden. It explicitly discloses irreversibility and the dual confirmation requirement, which is critical behavioral information. It does not mention what happens to associated data (e.g., stories, comments) or the response format, but for a delete tool this is a solid disclosure.

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

Conciseness5/5

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

Two sentences with no waste. The critical information (irreversibility, required confirmations) is front-loaded and immediately actionable.

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 deletion tool with no output schema and four parameters, the description covers the key aspects: what it deletes, the required confirmations, and irreversibility. It lacks explicit guidance on alternatives (archive_epic) and effects on related resources, but remains largely sufficient.

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 50%. The description adds meaning to confirm and confirm_delete by specifying required values ('CONFIRM_WRITE' and true), and it indirectly defines epic_id via 'by ID'. However, dry_run is not mentioned at all, leaving a gap in the undocumented parameter.

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

Purpose5/5

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

The description clearly states the action ('Permanently delete'), the resource ('a Shortcut epic'), and the mechanism ('by ID'). It also distinguishes from the sibling archive_epic by emphasizing irreversibility, making the tool's purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for permanent deletion but does not explicitly state when to use this tool versus archive_epic (which is reversible). Since archive_epic is a sibling tool, providing an explicit alternative would strengthen this dimension.

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/ptamb3/shortcut-mcp-server'

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