Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

create-epic

Create a new Shortcut epic to organize and manage large project initiatives within the Shortcut MCP Server.

Instructions

Create a new Shortcut epic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the epic
ownerNoThe user ID of the owner of the epic
descriptionNoA description of the epic
teamIdNoThe ID of a team to assign the epic to

Implementation Reference

  • The main handler function that executes the logic to create a new Shortcut epic using the client.createEpic method and returns a result.
    async createEpic({
    	name,
    	owner,
    	teamId: group_id,
    	description,
    }: {
    	name: string;
    	owner?: string;
    	teamId?: string;
    	description?: string;
    }): Promise<CallToolResult> {
    	const epic = await this.client.createEpic({
    		name,
    		group_id,
    		owner_ids: owner ? [owner] : undefined,
    		description,
    	});
    
    	return this.toResult(`Epic created with ID: ${epic.id}.`);
    }
  • Tool registration for 'create-epic', including the tool name, description, input schema, and reference to the handler function.
    server.tool(
    	"create-epic",
    	"Create a new Shortcut epic.",
    	{
    		name: z.string().describe("The name of the epic"),
    		owner: z.string().optional().describe("The user ID of the owner of the epic"),
    		description: z.string().optional().describe("A description of the epic"),
    		teamId: z.string().optional().describe("The ID of a team to assign the epic to"),
    	},
    	async (params) => await tools.createEpic(params),
    );
  • Zod schema defining the input parameters for the create-epic tool: name (required), owner, description, teamId (all optional except name).
    {
    	name: z.string().describe("The name of the epic"),
    	owner: z.string().optional().describe("The user ID of the owner of the epic"),
    	description: z.string().optional().describe("A description of the epic"),
    	teamId: z.string().optional().describe("The ID of a team to assign the epic to"),
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation tool, implying mutation, but doesn't address permissions, side effects, error conditions, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 for an agent to parse 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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after creation, potential constraints, or how it fits into the broader context of sibling tools. The agent lacks sufficient information to use this tool effectively beyond basic parameter passing.

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 schema description coverage is 100%, so the schema already documents all four parameters (name, owner, description, teamId) with clear descriptions. The tool description adds no additional parameter information beyond what's in the schema, which is acceptable given the high schema coverage, resulting in a baseline score of 3.

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 ('Create') and resource ('new Shortcut epic'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other creation tools like create-document, create-iteration, or create-story, which would require mentioning what distinguishes an epic from those other entities.

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., needing a team or owner), when not to use it, or how it relates to sibling tools like create-story or search-epics, leaving the agent to infer usage context.

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