Shortcut MCP Server

Create Shortcut Milestone

create_milestone

Create a milestone in Shortcut to group stories and track project phases. Provide a name and set optional state, description, categories, and completion date.

Instructions

Create a new milestone in Shortcut.

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": {
      "name": "<name>"
    },
    "name": "create_milestone"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`state`	No
`confirm`	No	Must be CONFIRM_WRITE to execute
`dry_run`	No
`categories`	No
`description`	No
`completed_at_override`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.4/5.0

Behavior1/5

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

With no annotations and no mention of side effects, confirmations, or the dry_run parameter, the description fails to disclose that this is a mutating operation requiring CONFIRM_WRITE to execute. It provides no behavioral context beyond the vague 'create' verb.

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

Conciseness3/5

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

The description is a single, concise sentence and is front-loaded, but it is under-specified for a tool with 7 parameters. It omits necessary operational details, so while it is not verbose, it is not appropriately sized for the tool's complexity.

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

Completeness1/5

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

The description is minimal and lacks any mention of return values, required confirmations, or parameter requirements. Given the 7-parameter schema and no output schema, the description is far from complete for reliable tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 7 parameters with only 14% description coverage, and the description adds no explanation of parameters like name, state, confirm, or dry_run. The description does not compensate for the low schema coverage, leaving parameter meaning entirely to the schema.

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 verb ('Create') and resource ('a new milestone in Shortcut'), making the tool's purpose unambiguous. It distinguishes itself from sibling update and list milestone tools by explicitly indicating creation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like update_milestone or list_milestones, nor does it mention any prerequisites or context. It simply states the action without any usage direction.

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

Deploy Server