Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

assign-current-user-as-owner

Assign yourself as the owner of a Shortcut story to take responsibility for its completion and management.

Instructions

Assign 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 executes the tool's core logic: fetches the story and current user, checks if the user is already an owner, and updates the story's owner_ids by appending the current user's ID.
    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}`);
    }
  • Zod input schema defining the required storyPublicId parameter.
    	storyPublicId: z.number().positive().describe("The public ID of the story"),
    },
  • Registers the tool with the MCP server, providing the tool name, description, input schema, and handler reference.
    server.tool(
    	"assign-current-user-as-owner",
    	"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),
    );
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 behavioral details. It doesn't disclose whether this requires specific permissions, if it's reversible, what happens to the previous owner, or any side effects. For a mutation tool with zero annotation coverage, this is insufficient.

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 with no wasted words. It is appropriately front-loaded and earns its place by clearly conveying the core action.

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 information about behavioral traits, return values, error conditions, or integration with sibling tools. Given the complexity of ownership changes, more context is needed for effective use.

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' well-documented in the schema. The description adds no additional parameter semantics beyond implying the story is identified by its public ID, 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 ('Assign') and resource ('owner of a story'), specifying it applies to the current user. It distinguishes from sibling 'unassign-current-user-as-owner' by being the opposite operation, though it doesn't explicitly differentiate from other story-modification tools like 'update-story'.

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' (which might also handle ownership changes) or 'unassign-current-user-as-owner'. The description implies usage for ownership assignment but lacks context about prerequisites, permissions, or typical scenarios.

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