Skip to main content
Glama
useshortcut

Shortcut MCP Server

Official
by useshortcut

iterations-create

Create new iterations in Shortcut project management by specifying name, dates, team, and description to organize work cycles.

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 contains the core logic for the 'iterations-create' tool, invoking the Shortcut client's `createIteration` method with mapped parameters and returning a success 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 defining the input parameters (name, startDate, endDate, optional teamId and description) for the 'iterations-create' tool.
    {
    	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"),
    },
  • Registration of the 'iterations-create' tool using `server.addToolWithWriteAccess`, providing the tool name, description, input schema, and handler reference.
    server.addToolWithWriteAccess(
    	"iterations-create",
    	"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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool creates something but doesn't mention permissions required, whether this is a mutating operation, what happens on success/failure, or any side effects. For a creation 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, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a creation tool and front-loads the essential information. Every word earns its place.

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 complexity of a creation operation with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what a 'Shortcut iteration' is, what happens after creation, or any behavioral context. The agent must rely entirely on the schema for parameter details and guess at outcomes.

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 all 5 parameters with clear descriptions (e.g., date formats, team assignment). The description adds no additional parameter information beyond what's in the schema. According to guidelines, 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 distinguishes from sibling tools like 'iterations-get-by-id' or 'iterations-search' by specifying creation rather than retrieval. However, it doesn't explicitly differentiate from other creation tools like 'epics-create' or 'stories-create' beyond the resource type.

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 prerequisites (e.g., needing teamId for assignment), when not to use it, or how it differs from other iteration-related tools like 'iterations-get-active' or 'iterations-search'. The agent must infer usage from the name and context 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