Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

stories-get-by-id

Retrieve a specific Shortcut story using its public ID to access project management details and data fields.

Instructions

Get a Shortcut story by public ID

Input Schema

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

Implementation Reference

  • Registration of the 'stories-get-by-id' MCP tool, including inline Zod schema and reference to the handler method.
    server.addToolWithReadAccess(
    	"stories-get-by-id",
    	"Get a Shortcut story by public ID",
    	{
    		storyPublicId: z.number().positive().describe("The public ID of the story to get"),
    		full: z
    			.boolean()
    			.optional()
    			.default(false)
    			.describe(
    				"True to return all story fields from the API. False to return a slim version that excludes uncommon fields",
    			),
    	},
    	async ({ storyPublicId, full }) => await tools.getStory(storyPublicId, full),
    );
  • Zod schema defining input parameters for the tool: storyPublicId (required number) and full (optional boolean).
    	storyPublicId: z.number().positive().describe("The public ID of the story to get"),
    	full: z
    		.boolean()
    		.optional()
    		.default(false)
    		.describe(
    			"True to return all story fields from the API. False to return a slim version that excludes uncommon fields",
    		),
    },
  • Handler function that fetches the story using ShortcutClientWrapper.getStory, handles errors, and formats the output using entityWithRelatedEntities and toResult.
    async getStory(storyPublicId: number, full = false) {
    	const story = await this.client.getStory(storyPublicId);
    
    	if (!story)
    		throw new Error(`Failed to retrieve Shortcut story with public ID: ${storyPublicId}.`);
    
    	return this.toResult(
    		`Story: sc-${storyPublicId}`,
    		await this.entityWithRelatedEntities(story, "story", full),
    	);
    }
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 of behavioral disclosure. While 'Get' implies a read operation, the description doesn't specify whether this requires authentication, has rate limits, returns partial or full data, or handles errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 zero wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly. Every part of the sentence earns its place by specifying the action, resource, and key identifier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (simple retrieval with 2 parameters), high schema coverage (100%), and no output schema, the description is minimally adequate. It states what the tool does but lacks context on usage, behavioral details, or output format. For a read operation with good schema support, this is borderline viable but leaves room for improvement.

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 fully documents both parameters ('storyPublicId' and 'full'). The description doesn't add any meaning beyond what the schema provides—it mentions 'public ID' but doesn't clarify format or source, and it doesn't explain the implications of the 'full' parameter. Baseline 3 is appropriate when the schema does all the work.

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 story by public ID'), making the purpose immediately understandable. It distinguishes this tool from other story-related tools like 'stories-search' or 'stories-create' by specifying retrieval by ID. However, it doesn't explicitly differentiate from 'stories-get-by-external-link' or other get-by-ID tools for different resources, 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'stories-search' for finding stories, 'stories-get-by-external-link' for alternative identifiers, or other get-by-ID tools for different resources. There's also no information about prerequisites or context for use.

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