Shortcut MCP Server

Bulk Delete Stories

bulk_delete_stories

Permanently delete multiple stories in bulk. Requires explicit confirmation to prevent accidental data loss.

Instructions

Permanently delete multiple stories at once. IRREVERSIBLE. Requires confirm_delete=true and confirm='CONFIRM_WRITE'.

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_ids": "<story_ids>"
    },
    "name": "bulk_delete_stories"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be CONFIRM_WRITE to execute
`dry_run`	No
`story_ids`	Yes	List of story IDs to delete
`confirm_delete`	No	Must be true to confirm permanent deletion

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the irreversible nature ('IRREVERSIBLE') and the double-confirmation requirement, which are critical safety traits for a destructive operation. It does not cover what happens to dependent data, but the core risk is clearly communicated.

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?

The description is a single, front-loaded sentence. It states the action first, then the critical caveat and requirements. Every word earns its place, with no fluff or repetition of schema details.

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 destructive bulk operation with no annotations or output schema, the description covers the essential aspects: action, scope, irreversibility, and required confirmations. The missing dry_run is a minor gap given the safety emphasis, but the tool remains invocable correctly based on the description alone.

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 75%, not quite the >80% threshold for baseline 3, so the description should compensate for the undocumented parameter. It does explain the semantics of confirm and confirm_delete, and story_ids is self-evident, but it omits any mention of dry_run, which is a meaningful gap for a delete operation.

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?

Clearly states the tool's function: 'Permanently delete multiple stories at once.' The verb 'delete' and resource 'stories' are specific, and 'multiple' distinguishes it from the sibling tool delete_story, which handles a single story.

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

Usage Guidelines4/5

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

The description provides clear context that this tool is for bulk deletion, contrasting with single-delete alternatives. It does not explicitly name alternatives or state when not to use it, but the 'multiple stories' phrasing is sufficient for an agent to select the appropriate tool.

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

Deploy Server