Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-assign-current-user

Assign yourself as the owner of a Shortcut story to manage project tasks directly from AI tools.

Instructions

Assign the current user as the owner of a story

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storyPublicIdYesThe public ID of the story

Implementation Reference

  • Implements the logic to assign the current user as an owner to the specified story. Fetches the story and current user, checks if already assigned, and updates the story's owner_ids if not.
    async assignCurrentUserAsOwner(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 already an owner of story sc-${storyPublicId}`);
    
    	await this.client.updateStory(storyPublicId, {
    		owner_ids: story.owner_ids.concat([currentUser.id]),
    	});
    
    	return this.toResult(`Assigned current user as owner of story sc-${storyPublicId}`);
    }
  • Registers the tool 'stories-assign-current-user' with its schema (storyPublicId: number) and links to the handler assignCurrentUserAsOwner.
    server.addToolWithWriteAccess(
    	"stories-assign-current-user",
    	"Assign the current user as the owner of a story",
    	{
    		storyPublicId: z.number().positive().describe("The public ID of the story"),
    	},
    	async ({ storyPublicId }) => await tools.assignCurrentUserAsOwner(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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Assign' implies a mutation, it lacks details on permissions needed, whether the operation is reversible, side effects (e.g., notifications), or error conditions. 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, direct sentence that efficiently conveys the core action without unnecessary words. It's front-loaded with the key verb and resource, making it easy to parse and understand immediately, with no wasted text.

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 no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, reversibility, or response format, and lacks usage guidelines. Given the complexity of ownership assignment, this leaves significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with the single parameter 'storyPublicId' fully documented in the schema. The description doesn't add parameter details beyond the schema, but with only one parameter and high coverage, a baseline of 4 is appropriate as the schema sufficiently explains the input.

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 ('Assign') and resource ('owner of a story'), with the subject being 'the current user'. It distinguishes from sibling tools like 'stories-unassign-current-user' by specifying the opposite operation, making the purpose unambiguous and well-differentiated.

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., user permissions), when not to use it (e.g., if already assigned), or compare it to similar tools like 'stories-update' for ownership changes, leaving the agent without contextual usage cues.

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