Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-create

Create a new Shortcut story by specifying a name and either a team or workflow, automatically placing it in the default workflow state for project management.

Instructions

Create a new Shortcut story. Name is required, and either a Team or Workflow must be specified:

  • If only Team is specified, we will use the default workflow for that team.

  • If Workflow is specified, it will be used regardless of Team. The story will be added to the default state for the workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the story. Required.
descriptionNoThe description of the story
typeNoThe type of the storyfeature
ownerNoThe user id of the owner of the story
epicNoThe epic id of the epic the story belongs to
iterationNoThe iteration id of the iteration the story belongs to
teamNoThe team ID or mention name of the team the story belongs to. Required unless a workflow is specified.
workflowNoThe workflow ID to add the story to. Required unless a team is specified.

Implementation Reference

  • Handler function that implements the core logic for creating a new Shortcut story. It resolves the workflow if only team is provided, fetches necessary data, calls the Shortcut client API to create the story, and returns a success message with the story ID.
    async createStory({
    	name,
    	description,
    	type,
    	owner,
    	epic,
    	iteration,
    	team,
    	workflow,
    }: {
    	name: string;
    	description?: string;
    	type: "feature" | "bug" | "chore";
    	owner?: string;
    	epic?: number;
    	iteration?: number;
    	team?: string;
    	workflow?: number;
    }) {
    	if (!workflow && !team) throw new Error("Team or Workflow has to be specified");
    
    	if (!workflow && team) {
    		const fullTeam = await this.client.getTeam(team);
    		workflow = fullTeam?.workflow_ids?.[0];
    	}
    
    	if (!workflow) throw new Error("Failed to find workflow for team");
    
    	const fullWorkflow = await this.client.getWorkflow(workflow);
    	if (!fullWorkflow) throw new Error("Failed to find workflow");
    
    	const story = await this.client.createStory({
    		name,
    		description,
    		story_type: type,
    		owner_ids: owner ? [owner] : [],
    		epic_id: epic,
    		iteration_id: iteration,
    		group_id: team,
    		workflow_state_id: fullWorkflow.default_state_id,
    	});
    
    	return this.toResult(`Created story: sc-${story.id}`);
    }
  • Tool registration block that adds the 'stories-create' tool to the MCP server, specifying the name, description, input schema using Zod, and the handler function.
    		server.addToolWithWriteAccess(
    			"stories-create",
    			`Create a new Shortcut story. 
    Name is required, and either a Team or Workflow must be specified:
    - If only Team is specified, we will use the default workflow for that team.
    - If Workflow is specified, it will be used regardless of Team.
    The story will be added to the default state for the workflow.
    `,
    			{
    				name: z.string().min(1).max(512).describe("The name of the story. Required."),
    				description: z.string().max(10_000).optional().describe("The description of the story"),
    				type: z
    					.enum(["feature", "bug", "chore"])
    					.default("feature")
    					.describe("The type of the story"),
    				owner: z.string().optional().describe("The user id of the owner of the story"),
    				epic: z.number().optional().describe("The epic id of the epic the story belongs to"),
    				iteration: z
    					.number()
    					.optional()
    					.describe("The iteration id of the iteration the story belongs to"),
    				team: z
    					.string()
    					.optional()
    					.describe(
    						"The team ID or mention name of the team the story belongs to. Required unless a workflow is specified.",
    					),
    				workflow: z
    					.number()
    					.optional()
    					.describe("The workflow ID to add the story to. Required unless a team is specified."),
    			},
    			async ({ name, description, type, owner, epic, iteration, team, workflow }) =>
    				await tools.createStory({
    					name,
    					description,
    					type,
    					owner,
    					epic,
    					iteration,
    					team,
    					workflow,
    				}),
    		);
  • Input schema using Zod for validating parameters of the stories-create tool: name (required), description, type, owner, epic, iteration, team, workflow.
    	name: z.string().min(1).max(512).describe("The name of the story. Required."),
    	description: z.string().max(10_000).optional().describe("The description of the story"),
    	type: z
    		.enum(["feature", "bug", "chore"])
    		.default("feature")
    		.describe("The type of the story"),
    	owner: z.string().optional().describe("The user id of the owner of the story"),
    	epic: z.number().optional().describe("The epic id of the epic the story belongs to"),
    	iteration: z
    		.number()
    		.optional()
    		.describe("The iteration id of the iteration the story belongs to"),
    	team: z
    		.string()
    		.optional()
    		.describe(
    			"The team ID or mention name of the team the story belongs to. Required unless a workflow is specified.",
    		),
    	workflow: z
    		.number()
    		.optional()
    		.describe("The workflow ID to add the story to. Required unless a team is specified."),
    },
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by explaining the creation behavior, default workflow usage, and that stories are added to the default state. However, it doesn't mention permission requirements, rate limits, or what happens on success/failure. For a creation tool with zero annotation coverage, this is good but not comprehensive.

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 perfectly structured and concise - three sentences with zero waste. It starts with the core purpose, then explains parameter requirements, and finally clarifies the team/workflow relationship and default state behavior. Every sentence earns its place by adding essential information.

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?

For a creation tool with 8 parameters, 100% schema coverage, but no annotations and no output schema, the description provides adequate context about the creation behavior and parameter relationships. However, it doesn't explain what the tool returns or potential error conditions, which would be helpful given the absence of output schema. The description is complete enough for basic usage but lacks some operational context.

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 schema already documents all 8 parameters thoroughly. The description adds some value by explaining the relationship between team and workflow parameters and clarifying that name is required, but doesn't provide additional semantic context beyond what's in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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 specific action ('Create a new Shortcut story') and resource ('story'), distinguishing it from sibling tools like 'stories-update' or 'stories-search'. It explicitly mentions the required parameters (name, team/workflow) which helps differentiate its purpose from other creation tools in the sibling list.

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

Usage Guidelines4/5

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

The description provides clear context on when to use this tool by specifying the required parameters (name and either team or workflow) and explaining the relationship between team and workflow parameters. However, it doesn't explicitly mention when NOT to use it or name specific alternatives among the many sibling tools, though the context implies it's for initial story creation rather than updates or other operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/useshortcut/mcp-server-shortcut'

If you have feedback or need assistance with the MCP directory API, please join our Discord server