Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

update-task

Modify task details, assign owners, or mark completion status within a Shortcut story to track project progress.

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

  • Registers the MCP tool 'update-task' with input schema using Zod and points to the updateTask handler method.
    server.tool(
    	"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),
    );
  • Implements the logic to update a task on a Shortcut story by fetching the story and task, then calling the client.updateTask method, and returning a result message.
    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);
    }
  • Zod schema defining the input parameters for the 'update-task' tool.
    	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"),
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update a task in a story' implies a mutation operation but doesn't specify what permissions are required, whether changes are reversible, what happens to existing task data not mentioned in parameters, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a tool with good schema documentation and follows a clear subject-verb-object structure that's immediately comprehensible.

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?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address important contextual aspects like error conditions, what happens when only required parameters are provided, whether partial updates are supported, or what the tool returns. The combination of mutation operation, multiple parameters, and lack of structured metadata requires more descriptive 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 all parameters are documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions. It doesn't explain relationships between parameters, provide examples, or clarify edge cases. The baseline of 3 is appropriate when the schema does the heavy lifting.

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. However, it doesn't differentiate from sibling tools like 'add-task-to-story' or 'update-story', which would require more specificity about what distinguishes this particular update operation.

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. With sibling tools like 'add-task-to-story', 'update-story', and 'assign-current-user-as-owner', there's no indication of when this specific task update operation is appropriate versus other modification tools. No prerequisites, exclusions, or alternative suggestions are mentioned.

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/ampcome-mcps/shortcut-mcp'

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