Shortcut MCP Server

Remove Label from Story

remove_story_label

Remove a label from a Shortcut story by providing the story ID and the remaining label IDs after removal. Confirmation required to apply changes.

Instructions

Remove a label from a Shortcut story. Provide the remaining label IDs after removal. Requires 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_id": "<story_id>",
      "label_ids": "<label_ids>"
    },
    "name": "remove_story_label"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be CONFIRM_WRITE to execute
`dry_run`	No
`story_id`	Yes
`label_ids`	Yes	Remaining label IDs after removing the unwanted label

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description discloses the confirmation requirement ('Requires confirm='CONFIRM_WRITE'') and the unusual semantics of label_ids ('Provide the remaining label IDs after removal'), which are important behavioral details. However, it does not mention the effect of dry_run, what happens if the label does not exist, or potential side effects beyond the removal. Since no annotations are present, the description carries the full burden, and it only partially meets it.

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 three short sentences, each serving a distinct purpose: stating the action, clarifying the parameter semantics, and noting the confirmation requirement. It is front-loaded with the primary function and avoids redundancy or extraneous detail.

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?

Given the lack of annotations and output schema, the description provides the essential purpose and the key parameter constraint, but it omits details about dry_run behavior and the outcome of an empty label_ids array. The tool is relatively simple, yet the description leaves some ambiguity about the full set of behaviors, making it adequately complete but not comprehensive.

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 input schema provides descriptions for label_ids and confirm, covering 50% of parameters. The description repeats and reinforces these, particularly the meaning of label_ids as the remaining labels, which is critical. However, story_id and dry_run lack descriptions in both the schema and the description, leaving a coverage gap. The description adds some value but does not fully compensate for the missing parameter information.

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 tool's function: 'Remove a label from a Shortcut story.' This is a specific verb and resource, and it distinguishes the tool from siblings like add_story_label, which performs the opposite operation. The purpose is explicit and 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 does not explicitly state when to use this tool versus alternatives such as update_story or add_story_label. It does mention the requirement for confirm='CONFIRM_WRITE', which provides guidance on invocation but not on selection among similar tools. The usage context is implied rather than directly stated.

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

Deploy Server