Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

unassign-current-user-as-owner

Remove yourself as owner from a Shortcut story to reassign responsibility or clear ownership when no longer needed.

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 handler function that implements the core logic: fetches the story and current user, verifies the user is an owner, filters them out of owner_ids, updates the story via client.updateStory, and returns a success message.
    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 MCP tool 'unassign-current-user-as-owner' with input schema for storyPublicId and handler reference to unassignCurrentUserAsOwner method.
    server.tool(
    	"unassign-current-user-as-owner",
    	"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 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. It implies a mutation (unassigning ownership) but doesn't disclose behavioral aspects like permissions needed, whether this is reversible, side effects, or error conditions. For a mutation tool with zero annotation coverage, this is inadequate.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 lacks details on permissions, side effects, return values, or error handling, which are critical 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?

Schema description coverage is 100%, with the single parameter 'storyPublicId' fully documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, so it 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 action ('unassign') and resource ('owner of a story') with specificity about the current user. It distinguishes from its sibling 'assign-current-user-as-owner' by indicating the opposite operation, though it doesn't explicitly mention this distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'update-story' for ownership changes, or prerequisites such as requiring the current user to already be the owner. The description only states what it does, not when it's appropriate.

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