Shortcut MCP Server

Create Shortcut Iteration

create_iteration

Create a new iteration (sprint) in Shortcut by specifying name, start and end dates, and optional team, label, or follower assignments.

Instructions

Create a new iteration (sprint) 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>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "create_iteration"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`confirm`	No	Must be CONFIRM_WRITE to execute
`dry_run`	No
`end_date`	Yes	ISO 8601 date, e.g. 2026-03-24
`group_ids`	No
`label_ids`	No
`start_date`	Yes	ISO 8601 date, e.g. 2026-03-10
`description`	No
`follower_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It says only 'Create a new iteration,' omitting the CONFIRM_WRITE requirement, the dry_run safety mechanism, and any side effects or permission needs. The agent receives no warning that this mutation requires explicit confirmation, which is a critical behavioral gap.

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

Conciseness4/5

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

The description is a single, front-loaded sentence with no wasted words. It conveys the core purpose efficiently, though it is minimal and could be slightly more informative without hurting conciseness.

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?

This tool has 9 parameters, no annotations, no output schema, and a safety confirmation requirement. A one-sentence description is grossly insufficient for an agent to invoke it correctly. It fails to mention required fields, the confirmation flow, or how creation interacts with other iteration tools.

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 description adds no meaning for any of the nine parameters. Schema description coverage is only 33%, and the description fails to compensate for the undocumented parameters like confirm, dry_run, group_ids, label_ids, and follower_ids. Even common parameters like name are left entirely to the agent's inference.

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 states a specific verb and resource: 'Create a new iteration (sprint) in Shortcut.' This clearly distinguishes it from sibling tools like update_iteration, delete_iteration, get_iteration, and list_iterations by its create action.

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 create_iteration versus update_iteration or other iteration tools, no prerequisites such as the need for start_date and end_date, and no mention of alternatives. It only states the bare action without any decision support.

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

Deploy Server