Skip to main content
Glama
Sign In
shortcut-mcp

shortcut-mcp

by idyll
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create-story

Create a new story in Shortcut by specifying title, description, and story type. Optionally link to a team, epic, or workflow state.

Instructions

Create a new story 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>",
      "description": "<description>",
      "story_type": "<story_type>"
    },
    "name": "create-story"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesStory title
descriptionYesStory description
story_typeYesStory type (feature, bug, chore)
team_idNoTeam ID to create the story in (group_id in Shortcut API)
team_nameNoTeam name to create the story in (alternative to team_id)
epic_idNoEpic ID to associate with the story
epic_nameNoEpic name to associate with the story (alternative to epic_id)
workflow_state_nameNoWorkflow state name (e.g., 'Backlog', 'In Development'). Defaults to 'Backlog' if not specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as side effects, permissions, rate limits, or outcome. The minimal description fails to add transparency.

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?

Single sentence with no unnecessary words. Efficient and front-loaded.

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

Completeness2/5

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

Given 8 parameters and no output schema, the description is too incomplete. It does not explain what the tool returns or how it behaves with multiple optional parameters like team_id vs team_name.

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 description coverage is 100%, so the baseline is 3. The description 'Create a new story in Shortcut' adds no extra parameter meaning beyond what the schema already provides.

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 action ('create') and resource ('story') in a specific system ('Shortcut'). It differentiates well from sibling tools like 'create-epic' and 'create-objective'.

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?

No guidance on when to use this tool versus alternatives (e.g., 'update-story', 'search-stories'). No prerequisites or context for when not to use it.

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

Deploy Server

Other Tools