Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

get-iteration-stories

Retrieve stories from a specific Shortcut iteration using its public ID, with optional story descriptions for detailed project tracking.

Instructions

Get stories in a specific iteration by iteration public ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iterationPublicIdYesThe public ID of the iteration
includeStoryDescriptionsNoIndicate whether story descriptions should be included. Including descriptions may take longer and will increase the size of the response.

Implementation Reference

  • The handler function that implements the core logic of the 'get-iteration-stories' tool. It fetches stories from a Shortcut iteration using the client and returns a formatted result.
    async getIterationStories(iterationPublicId: number, includeDescription: boolean) {
    	const { stories } = await this.client.listIterationStories(
    		iterationPublicId,
    		includeDescription,
    	);
    
    	if (!stories)
    		throw new Error(
    			`Failed to retrieve Shortcut stories in iteration with public ID: ${iterationPublicId}.`,
    		);
    
    	return this.toResult(
    		`Result (${stories.length} stories found):`,
    		await this.entitiesWithRelatedEntities(stories, "stories"),
    	);
    }
  • Zod schema defining the input parameters for the tool: required iterationPublicId (positive number) and optional includeStoryDescriptions (boolean, default false).
    	iterationPublicId: z.number().positive().describe("The public ID of the iteration"),
    	includeStoryDescriptions: z
    		.boolean()
    		.optional()
    		.default(false)
    		.describe(
    			"Indicate whether story descriptions should be included. Including descriptions may take longer and will increase the size of the response.",
    		),
    },
  • Registers the 'get-iteration-stories' tool with the MCP server, providing name, description, input schema, and a handler that delegates to the getIterationStories method.
    server.tool(
    	"get-iteration-stories",
    	"Get stories in a specific iteration by iteration public ID",
    	{
    		iterationPublicId: z.number().positive().describe("The public ID of the iteration"),
    		includeStoryDescriptions: z
    			.boolean()
    			.optional()
    			.default(false)
    			.describe(
    				"Indicate whether story descriptions should be included. Including descriptions may take longer and will increase the size of the response.",
    			),
    	},
    	async ({ iterationPublicId, includeStoryDescriptions }) =>
    		await tools.getIterationStories(iterationPublicId, includeStoryDescriptions),
    );
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 mentions that including descriptions 'may take longer and will increase the size of the response' (which is actually in the schema, not the description), but the description itself lacks behavioral context about permissions needed, rate limits, pagination, or what format/structure the returned stories will have.

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 unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the core functionality.

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 retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what data is returned (story fields, format), whether there are pagination considerations, authentication requirements, or error conditions. The sibling tools include multiple story-related operations, making context about this specific retrieval method particularly important.

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 meaningful parameter semantics beyond what's in the schema - it mentions 'by iteration public ID' which corresponds to the iterationPublicId parameter, but provides no additional context about valid values or usage patterns.

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 stories') and the target resource ('in a specific iteration by iteration public ID'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'search-stories' or 'get-story', which could retrieve similar data through different mechanisms.

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 like 'search-stories' or 'get-story'. It mentions the specific iteration requirement but doesn't explain why one would choose this tool over other story-retrieval methods available in the sibling list.

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