Shortcut MCP Server

Bulk Move Stories

bulk_move_stories

Move multiple stories to a different project or workflow state in one operation. Update story destinations together to reorganize your Shortcut workspace.

Instructions

Move multiple stories to a different project and/or workflow state.

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_move_stories"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be CONFIRM_WRITE to execute
`dry_run`	No
`epic_id`	No	Target epic ID
`story_ids`	Yes	List of story IDs to move
`project_id`	No	Target project ID
`workflow_state_id`	No	Target workflow state ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral transparency. It only states the action 'move' without disclosing the confirmation requirement (confirm parameter), dry-run support, or any side effects or permissions.

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 concise sentence with no wasted words, making it efficient. However, the brevity contributes to lack of detail, but conciseness itself is well-handled.

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?

For a mutating tool with a confirmation guard and dry-run option, the description is inadequate. It doesn't mention required confirm, the dry_run parameter, or the epic_id option, and there's no output schema to compensate. Agents would be under-informed.

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 83% (5 of 6 params have descriptions). The description adds minimal value by mentioning project and workflow state, but doesn't explain confirm or dry_run semantics, which are critical for safe execution.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool moves multiple stories to a different project and/or workflow state, which is a specific batch operation. However, it omits the ability to move to an epic (epic_id parameter), making the purpose slightly incomplete.

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 compared to siblings like bulk_update_stories or transition_story_state. It just states the action without context or alternatives.

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

Deploy Server