Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

iterations-get-by-id

Retrieve a specific iteration from Shortcut project management using its public ID to access detailed information about project timelines and progress.

Instructions

Get a Shortcut iteration by public ID

Input Schema

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

Implementation Reference

  • Handler function that fetches the iteration by public ID using the client, handles errors, and formats the result using base methods.
    async getIteration(iterationPublicId: number, full = false) {
    	const iteration = await this.client.getIteration(iterationPublicId);
    
    	if (!iteration)
    		throw new Error(
    			`Failed to retrieve Shortcut iteration with public ID: ${iterationPublicId}.`,
    		);
    
    	return this.toResult(
    		`Iteration: ${iterationPublicId}`,
    		await this.entityWithRelatedEntities(iteration, "iteration", full),
    	);
    }
  • Zod schema defining input parameters: iterationPublicId (required number) and full (optional boolean, default false).
    {
    	iterationPublicId: z.number().positive().describe("The public ID of the iteration to get"),
    	full: z
    		.boolean()
    		.optional()
    		.default(false)
    		.describe(
    			"True to return all iteration fields from the API. False to return a slim version that excludes uncommon fields",
    		),
    },
  • Registration of the 'iterations-get-by-id' tool using server.addToolWithReadAccess, including name, description, input schema, and handler lambda that delegates to getIteration method.
    server.addToolWithReadAccess(
    	"iterations-get-by-id",
    	"Get a Shortcut iteration by public ID",
    	{
    		iterationPublicId: z.number().positive().describe("The public ID of the iteration to get"),
    		full: z
    			.boolean()
    			.optional()
    			.default(false)
    			.describe(
    				"True to return all iteration fields from the API. False to return a slim version that excludes uncommon fields",
    			),
    	},
    	async ({ iterationPublicId, full }) => await tools.getIteration(iterationPublicId, full),
    );
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 the tool retrieves an iteration but doesn't mention whether it's a read-only operation, what permissions are required, potential rate limits, or error handling. This leaves significant gaps in understanding the tool's behavior beyond basic retrieval.

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, front-loaded sentence that efficiently conveys the core purpose without unnecessary words. It avoids redundancy and gets straight to the point, 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 the lack of annotations and output schema, the description is insufficient for a tool with parameters. It doesn't explain return values, error conditions, or behavioral nuances, leaving the agent with incomplete context for proper invocation and result interpretation.

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 input schema has 100% description coverage, so the schema already documents both parameters ('iterationPublicId' and 'full') thoroughly. The description adds no additional meaning beyond implying retrieval by ID, which aligns with the schema. This meets the baseline for high schema coverage.

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 iteration by public ID'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'iterations-get-active' or 'iterations-get-upcoming' beyond specifying retrieval by ID, which slightly limits its distinctiveness.

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 such as 'iterations-search' or other iteration-related tools. It lacks context about prerequisites, use cases, or exclusions, leaving the agent to infer usage from the tool name alone.

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