Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-unassign-current-user

Remove yourself as the assigned owner from a Shortcut story to clear your workload or reassign tasks.

Instructions

Unassign the current user as the owner of a story

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storyPublicIdYesThe public ID of the story

Implementation Reference

  • The main handler function for the tool. It fetches the story and current user, verifies the current user is an owner, then updates the story by removing the current user from the owner_ids array.
    async unassignCurrentUserAsOwner(storyPublicId: number) {
    	const story = await this.client.getStory(storyPublicId);
    
    	if (!story)
    		throw new Error(`Failed to retrieve Shortcut story with public ID: ${storyPublicId}`);
    
    	const currentUser = await this.client.getCurrentUser();
    
    	if (!currentUser) throw new Error("Failed to retrieve current user");
    
    	if (!story.owner_ids.includes(currentUser.id))
    		return this.toResult(`Current user is not an owner of story sc-${storyPublicId}`);
    
    	await this.client.updateStory(storyPublicId, {
    		owner_ids: story.owner_ids.filter((ownerId) => ownerId !== currentUser.id),
    	});
    
    	return this.toResult(`Unassigned current user as owner of story sc-${storyPublicId}`);
    }
  • Registers the tool 'stories-unassign-current-user' with the MCP server using addToolWithWriteAccess, linking to the handler function.
    server.addToolWithWriteAccess(
    	"stories-unassign-current-user",
    	"Unassign the current user as the owner of a story",
    	{
    		storyPublicId: z.number().positive().describe("The public ID of the story"),
    	},
    	async ({ storyPublicId }) => await tools.unassignCurrentUserAsOwner(storyPublicId),
    );
  • Zod schema defining the input parameter: storyPublicId as a positive number.
    {
    	storyPublicId: z.number().positive().describe("The public ID of the story"),
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention if this requires specific permissions, whether it's reversible, what happens to the story after unassignment, or any rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand quickly.

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 the tool's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects, error handling, or return values, which are crucial for safe and effective use by an AI agent.

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?

The description adds no parameter semantics beyond what the input schema provides, which has 100% coverage and fully documents the 'storyPublicId' parameter. Since schema coverage is high, the baseline score is 3, as the description doesn't need to compensate but also doesn't add extra value.

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 action ('Unassign') and resource ('the current user as the owner of a story'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'stories-assign-current-user' or 'stories-update', which could also affect story ownership, so it doesn't reach the highest score.

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, such as 'stories-assign-current-user' for assigning ownership or 'stories-update' for other modifications. There's no mention of prerequisites, context, or exclusions, leaving usage unclear.

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