Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

epics-create

Create new epics in Shortcut project management by specifying name, owner, description, and team assignment for organizing large initiatives.

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 for the 'epics-create' tool. It destructures the input parameters, calls this.client.createEpic to create the epic in Shortcut, and returns a success message with the new epic ID.
    	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}.`);
    	}
    }
  • Registration of the 'epics-create' tool using server.addToolWithWriteAccess, including the tool name, description, input schema with Zod validators, and the handler function that delegates to createEpic.
    server.addToolWithWriteAccess(
    	"epics-create",
    	"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),
    );
  • Input schema for the 'epics-create' tool, defining parameters with Zod: required name (string), optional owner, description, and teamId (all strings).
    {
    	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 'Create' which implies a write/mutation operation, but doesn't specify required permissions, whether the operation is idempotent, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps for the agent.

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 states the core purpose without any wasted words. It's appropriately sized for a straightforward creation tool and is front-loaded with the essential information.

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 insufficiently complete. It doesn't explain what happens after creation (e.g., returns the created epic object, returns only success status), error conditions, or system behavior. The agent lacks crucial context about the tool's operation and results.

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%, 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. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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. It distinguishes from sibling tools like 'epics-get-by-id' and 'epics-search' by specifying creation rather than retrieval. However, it doesn't explicitly differentiate from other creation tools like 'stories-create' or 'iterations-create' beyond the resource type.

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., required permissions), when not to use it, or how it differs from similar creation tools like 'stories-create' or 'iterations-create' beyond the resource type. The agent must infer usage solely from the tool name and 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/useshortcut/mcp-server-shortcut'

If you have feedback or need assistance with the MCP directory API, please join our Discord server