Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

create-iteration

Create a new iteration in Shortcut project management by specifying name, start date, end date, and optional team assignment or description.

Instructions

Create a new Shortcut iteration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the iteration
startDateYesThe start date of the iteration in YYYY-MM-DD format
endDateYesThe end date of the iteration in YYYY-MM-DD format
teamIdNoThe ID of a team to assign the iteration to
descriptionNoA description of the iteration

Implementation Reference

  • The `createIteration` method that executes the tool logic: creates a new Shortcut iteration using the client, handles parameters like name, dates, team, description, and returns a result message with the new iteration ID.
    async createIteration({
    	name,
    	startDate,
    	endDate,
    	teamId,
    	description,
    }: {
    	name: string;
    	startDate: string;
    	endDate: string;
    	teamId?: string;
    	description?: string;
    }): Promise<CallToolResult> {
    	const iteration = await this.client.createIteration({
    		name,
    		start_date: startDate,
    		end_date: endDate,
    		group_ids: teamId ? [teamId] : undefined,
    		description,
    	});
    
    	if (!iteration) throw new Error(`Failed to create the iteration.`);
    
    	return this.toResult(`Iteration created with ID: ${iteration.id}.`);
    }
  • Zod schema validating the input parameters for the 'create-iteration' tool: name (required string), startDate and endDate (strings in YYYY-MM-DD), optional teamId and description.
    	name: z.string().describe("The name of the iteration"),
    	startDate: z.string().describe("The start date of the iteration in YYYY-MM-DD format"),
    	endDate: z.string().describe("The end date of the iteration in YYYY-MM-DD format"),
    	teamId: z.string().optional().describe("The ID of a team to assign the iteration to"),
    	description: z.string().optional().describe("A description of the iteration"),
    },
  • Registers the 'create-iteration' tool with the MCP server in the IterationTools static create method, linking the schema and handler.
    server.tool(
    	"create-iteration",
    	"Create a new Shortcut iteration",
    	{
    		name: z.string().describe("The name of the iteration"),
    		startDate: z.string().describe("The start date of the iteration in YYYY-MM-DD format"),
    		endDate: z.string().describe("The end date of the iteration in YYYY-MM-DD format"),
    		teamId: z.string().optional().describe("The ID of a team to assign the iteration to"),
    		description: z.string().optional().describe("A description of the iteration"),
    	},
    	async (params) => await tools.createIteration(params),
    );
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 creation operation but doesn't mention permissions needed, whether this is a write operation that modifies data, what happens on success/failure, or any rate limits. 'Create' implies mutation, but the description lacks crucial behavioral details for a tool with no annotation coverage.

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 communicates the core purpose without any wasted words. It's appropriately sized and 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 creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'Shortcut iteration' is in this context, what happens after creation, or what the tool returns. The agent must rely entirely on the input schema and tool name without adequate contextual guidance.

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 all parameters are documented in the schema. The description adds no additional parameter information beyond what's already 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 iteration'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'create-epic' or 'create-story', but the specific mention of 'iteration' provides adequate differentiation for this context.

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 'create-epic' or 'create-story'. It doesn't mention prerequisites, context, or any comparison with sibling tools, leaving the agent to infer usage solely from the tool name and schema.

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