Skip to main content
Glama
Sign In
Shortcut MCP Server

Shortcut MCP Server

by ptamb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Shortcut Story

delete_story

Permanently delete a Shortcut story by its ID. This irreversible action requires explicit confirmation to execute.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "story_id": "<story_id>"
    },
    "name": "delete_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be CONFIRM_WRITE to execute
dry_runNo
story_idYes
confirm_deleteNoMust be true to confirm permanent deletion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

It discloses irreversibility and required confirmation parameters, adding safety context beyond the schema. However, it omits the dry_run parameter's behavior, which could make the absolute statement 'permanently delete' misleading. With no annotations, the description should clarify this, but it doesn't.

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, front-loaded with purpose and critical safety information. No unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers core intent and required confirmations, but it fails to mention dry_run behavior, which is part of the schema. This is a notable gap for a delete operation, leaving ambiguity about whether the tool always deletes or can simulate.

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?

The description clarifies that both confirm and confirm_delete are required (schema only marks story_id required) and states their expected values, adding meaning beyond the schema. However, it does not address dry_run, and schema description coverage is only 50%, so not all parameters are compensated.

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 uses a specific verb 'delete' and resource 'Shortcut story' with clear scope 'by ID'. It distinguishes itself from sibling deletion tools like delete_epic or delete_project.

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 warns that deletion is IRREVERSIBLE, implying it should only be used when permanent removal is intended. However, it does not explicitly mention alternatives like archive_story or bulk_delete_stories, so guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools