Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-update-task

Update task details like description, owners, or completion status within a Shortcut story to track progress and assign responsibilities.

Instructions

Update a task in a story

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storyPublicIdYesThe public ID of the story
taskPublicIdYesThe public ID of the task
taskDescriptionNoThe description of the task
taskOwnerIdsNoArray of user IDs to assign as owners of the task
isCompletedNoWhether the task is completed or not

Implementation Reference

  • Handler function for the 'stories-update-task' tool. Updates a story task's description, owners, or completion status via the ShortcutClientWrapper.
    async updateTask({
    	storyPublicId,
    	taskPublicId,
    	taskDescription,
    	taskOwnerIds,
    	isCompleted,
    }: {
    	storyPublicId: number;
    	taskPublicId: number;
    	taskDescription?: string;
    	taskOwnerIds?: string[];
    	isCompleted?: boolean;
    }) {
    	if (!storyPublicId) throw new Error("Story public ID is required");
    	if (!taskPublicId) throw new Error("Task public ID is required");
    
    	const story = await this.client.getStory(storyPublicId);
    	if (!story)
    		throw new Error(`Failed to retrieve Shortcut story with public ID: ${storyPublicId}`);
    
    	const task = await this.client.getTask(storyPublicId, taskPublicId);
    	if (!task) throw new Error(`Failed to retrieve Shortcut task with public ID: ${taskPublicId}`);
    
    	const updatedTask = await this.client.updateTask(storyPublicId, taskPublicId, {
    		description: taskDescription,
    		ownerIds: taskOwnerIds,
    		isCompleted,
    	});
    
    	let message = `Updated task for story sc-${storyPublicId}. Task ID: ${updatedTask.id}.`;
    	if (isCompleted) {
    		message = `Completed task for story sc-${storyPublicId}. Task ID: ${updatedTask.id}.`;
    	}
    
    	return this.toResult(message);
    }
  • Input schema (Zod) for the 'stories-update-task' tool defining parameters: storyPublicId, taskPublicId, taskDescription, taskOwnerIds, isCompleted.
    {
    	storyPublicId: z.number().positive().describe("The public ID of the story"),
    	taskPublicId: z.number().positive().describe("The public ID of the task"),
    	taskDescription: z.string().optional().describe("The description of the task"),
    	taskOwnerIds: z
    		.array(z.string())
    		.optional()
    		.describe("Array of user IDs to assign as owners of the task"),
    	isCompleted: z.boolean().optional().describe("Whether the task is completed or not"),
    },
  • Registration of the 'stories-update-task' tool in StoryTools.create() using server.addToolWithWriteAccess, specifying name, description, schema, and handler.
    server.addToolWithWriteAccess(
    	"stories-update-task",
    	"Update a task in a story",
    	{
    		storyPublicId: z.number().positive().describe("The public ID of the story"),
    		taskPublicId: z.number().positive().describe("The public ID of the task"),
    		taskDescription: z.string().optional().describe("The description of the task"),
    		taskOwnerIds: z
    			.array(z.string())
    			.optional()
    			.describe("Array of user IDs to assign as owners of the task"),
    		isCompleted: z.boolean().optional().describe("Whether the task is completed or not"),
    	},
    	async (params) => await tools.updateTask(params),
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't specify permissions required, whether changes are reversible, error handling, or response format. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented, justifying a low score.

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, efficient sentence with zero wasted words. It's front-loaded with the core action ('Update a task in a story'), making it immediately scannable. Every word earns its place, meeting the highest standard for conciseness.

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 this is a mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects, error conditions, or what the tool returns. For a tool that modifies data, this level of brevity leaves too many contextual gaps, scoring a 2.

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%, with all parameters clearly documented in the schema itself (e.g., storyPublicId, taskPublicId, taskDescription). The description adds no additional parameter semantics beyond implying that task updates are possible. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Update a task in a story' clearly states the verb ('update') and resource ('task in a story'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'stories-add-task' (creation) and 'stories-update' (general story updates), though it doesn't explicitly mention what fields can be updated. This is specific enough for a 4, but lacks the detailed scope that would warrant a 5.

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 versus alternatives. It doesn't mention prerequisites (e.g., needing existing story and task IDs), compare it to 'stories-update' for broader story modifications, or specify use cases like marking tasks complete or reassigning owners. With no usage context provided, this scores a 2.

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