Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

epics-get-by-id

Retrieve a Shortcut epic using its public ID to access project management data, with options for full or slim field returns.

Instructions

Get a Shortcut epic by public ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
epicPublicIdYesThe public ID of the epic to get
fullNoTrue to return all epic fields from the API. False to return a slim version that excludes uncommon fields

Implementation Reference

  • The main handler function that executes the tool logic: fetches the epic by public ID from the Shortcut client, handles errors, and formats the result using inherited helper methods.
    async getEpic(epicPublicId: number, full = false) {
    	const epic = await this.client.getEpic(epicPublicId);
    
    	if (!epic) throw new Error(`Failed to retrieve Shortcut epic with public ID: ${epicPublicId}`);
    
    	return this.toResult(
    		`Epic: ${epicPublicId}`,
    		await this.entityWithRelatedEntities(epic, "epic", full),
    	);
    }
  • Input schema defined using Zod for validating tool parameters: epicPublicId (positive number) and optional full (boolean, default false).
    {
    	epicPublicId: z.number().positive().describe("The public ID of the epic to get"),
    	full: z
    		.boolean()
    		.optional()
    		.default(false)
    		.describe(
    			"True to return all epic fields from the API. False to return a slim version that excludes uncommon fields",
    		),
    },
  • Registers the "epics-get-by-id" tool on the CustomMcpServer with read access, description, input schema, and a handler that delegates to the getEpic method.
    server.addToolWithReadAccess(
    	"epics-get-by-id",
    	"Get a Shortcut epic by public ID",
    	{
    		epicPublicId: z.number().positive().describe("The public ID of the epic to get"),
    		full: z
    			.boolean()
    			.optional()
    			.default(false)
    			.describe(
    				"True to return all epic fields from the API. False to return a slim version that excludes uncommon fields",
    			),
    	},
    	async ({ epicPublicId, full }) => await tools.getEpic(epicPublicId, full),
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't mention authentication requirements, rate limits, error conditions, or what the return format looks like. This leaves significant gaps for a tool that presumably fetches data.

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 exactly what the tool does with zero wasted words. It's appropriately sized for a simple retrieval operation and front-loads 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 read operation with no annotations and no output schema, the description is insufficient. It doesn't explain what data is returned, how errors are handled, or any behavioral constraints. Given the lack of structured metadata, the description should provide more context about the operation's behavior 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 fully documents both parameters. The description doesn't add any additional meaning beyond what's in the schema, such as explaining the significance of the 'full' parameter's slim vs. complete response options. This meets the baseline expectation when schema coverage is high.

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 ('Get') and resource ('a Shortcut epic by public ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'epics-search' or 'epics-create' beyond the basic operation type, which prevents a perfect score.

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 'epics-search' or 'epics-create'. The description only states what the tool does, not when it's appropriate or what prerequisites might exist.

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