Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-update

Modify existing Shortcut stories by updating specific fields like name, description, type, or workflow state using partial updates.

Instructions

Update an existing Shortcut story. Only provide fields you want to update. The story public ID will always be included in updates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storyPublicIdYesThe public ID of the story to update
nameNoThe name of the story
descriptionNoThe description of the story
typeNoThe type of the story
epicNoThe epic id of the epic the story belongs to, or null to unset
estimateNoThe point estimate of the story, or null to unset
iterationNoThe iteration id of the iteration the story belongs to, or null to unset
owner_idsNoArray of user UUIDs to assign as owners of the story
workflow_state_idNoThe workflow state ID to move the story to
labelsNoLabels to assign to the story

Implementation Reference

  • The handler function that executes the core logic for updating a Shortcut story. It validates inputs, maps parameters to API format, verifies the story exists, and calls the client to perform the update.
    async updateStory({
    	storyPublicId,
    	...updates
    }: {
    	storyPublicId: number;
    	name?: string;
    	description?: string;
    	type?: "feature" | "bug" | "chore";
    	epic?: number | null;
    	estimate?: number | null;
    	iteration?: number | null;
    	owner_ids?: string[];
    	workflow_state_id?: number;
    	labels?: Array<{
    		name: string;
    		color?: string;
    		description?: string;
    	}>;
    }) {
    	if (!storyPublicId) throw new Error("Story public ID is required");
    
    	// Verify the story exists
    	const story = await this.client.getStory(storyPublicId);
    	if (!story)
    		throw new Error(`Failed to retrieve Shortcut story with public ID: ${storyPublicId}`);
    
    	// Convert API parameters
    	const updateParams: Record<string, unknown> = {};
    
    	if (updates.name !== undefined) updateParams.name = updates.name;
    	if (updates.description !== undefined) updateParams.description = updates.description;
    	if (updates.type !== undefined) updateParams.story_type = updates.type;
    	if (updates.epic !== undefined) updateParams.epic_id = updates.epic;
    	if (updates.estimate !== undefined) updateParams.estimate = updates.estimate;
    	if (updates.iteration !== undefined) updateParams.iteration_id = updates.iteration;
    	if (updates.owner_ids !== undefined) updateParams.owner_ids = updates.owner_ids;
    	if (updates.workflow_state_id !== undefined)
    		updateParams.workflow_state_id = updates.workflow_state_id;
    	if (updates.labels !== undefined) updateParams.labels = updates.labels;
    
    	// Update the story
    	const updatedStory = await this.client.updateStory(storyPublicId, updateParams);
    
    	return this.toResult(`Updated story sc-${storyPublicId}. Story URL: ${updatedStory.app_url}`);
    }
  • Zod schema defining the input parameters for the stories-update tool, including storyPublicId (required) and various optional update fields.
    	storyPublicId: z.number().positive().describe("The public ID of the story to update"),
    	name: z.string().max(512).optional().describe("The name of the story"),
    	description: z.string().max(10_000).optional().describe("The description of the story"),
    	type: z.enum(["feature", "bug", "chore"]).optional().describe("The type of the story"),
    	epic: z
    		.number()
    		.nullable()
    		.optional()
    		.describe("The epic id of the epic the story belongs to, or null to unset"),
    	estimate: z
    		.number()
    		.nullable()
    		.optional()
    		.describe("The point estimate of the story, or null to unset"),
    	iteration: z
    		.number()
    		.nullable()
    		.optional()
    		.describe("The iteration id of the iteration the story belongs to, or null to unset"),
    	owner_ids: z
    		.array(z.string())
    		.optional()
    		.describe("Array of user UUIDs to assign as owners of the story"),
    	workflow_state_id: z
    		.number()
    		.optional()
    		.describe("The workflow state ID to move the story to"),
    	labels: z
    		.array(
    			z.object({
    				name: z.string().describe("The name of the label"),
    				color: z.string().optional().describe("The color of the label"),
    				description: z.string().optional().describe("The description of the label"),
    			}),
    		)
    		.optional()
    		.describe("Labels to assign to the story"),
    },
  • Registration of the stories-update tool with the MCP server, including name, description, input schema, and handler reference.
    server.addToolWithWriteAccess(
    	"stories-update",
    	"Update an existing Shortcut story. Only provide fields you want to update. The story public ID will always be included in updates.",
    	{
    		storyPublicId: z.number().positive().describe("The public ID of the story to update"),
    		name: z.string().max(512).optional().describe("The name of the story"),
    		description: z.string().max(10_000).optional().describe("The description of the story"),
    		type: z.enum(["feature", "bug", "chore"]).optional().describe("The type of the story"),
    		epic: z
    			.number()
    			.nullable()
    			.optional()
    			.describe("The epic id of the epic the story belongs to, or null to unset"),
    		estimate: z
    			.number()
    			.nullable()
    			.optional()
    			.describe("The point estimate of the story, or null to unset"),
    		iteration: z
    			.number()
    			.nullable()
    			.optional()
    			.describe("The iteration id of the iteration the story belongs to, or null to unset"),
    		owner_ids: z
    			.array(z.string())
    			.optional()
    			.describe("Array of user UUIDs to assign as owners of the story"),
    		workflow_state_id: z
    			.number()
    			.optional()
    			.describe("The workflow state ID to move the story to"),
    		labels: z
    			.array(
    				z.object({
    					name: z.string().describe("The name of the label"),
    					color: z.string().optional().describe("The color of the label"),
    					description: z.string().optional().describe("The description of the label"),
    				}),
    			)
    			.optional()
    			.describe("Labels to assign to the story"),
    	},
    	async (params) => await tools.updateStory(params),
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions that updates are partial ('Only provide fields you want to update') and that the story public ID is always included, which adds some behavioral context. However, it lacks details on permissions, error handling, side effects, or response format, which are critical for a mutation tool.

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 two sentences with zero waste, front-loading the core action and following with a key behavioral note. Every word serves a purpose, making it highly efficient.

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 mutation tool with no annotations and no output schema, the description is incomplete. It covers the basic update mechanism but misses critical details like response structure, error conditions, and permission requirements. The high schema coverage helps, but more behavioral context is needed.

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 fully documents all 10 parameters. The description adds minimal value by implying partial updates, but doesn't provide additional semantics beyond what's in the schema. This meets the baseline for high schema coverage.

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 verb ('Update') and resource ('an existing Shortcut story'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'stories-create' or 'stories-update-task', which would be needed for a perfect score.

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

Usage Guidelines3/5

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

The description provides some usage guidance by specifying 'Only provide fields you want to update,' which implies partial updates are supported. However, it doesn't mention when to use this tool versus alternatives like 'stories-create' or 'stories-update-task,' nor does it discuss prerequisites or exclusions.

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