Skip to main content
Glama
goto-software

plane-mcp-server

create_cycle

Create a new cycle for a project by providing the cycle name, owner, and optional start/end dates, description, timezone, or external system references.

Instructions

Create a new cycle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
nameYesCycle name
owned_byYesUUID of the user who owns the cycle
descriptionNoCycle description
start_dateNoCycle start date (ISO 8601 format)
end_dateNoCycle end date (ISO 8601 format)
external_sourceNoExternal system source name
external_idNoExternal system identifier
timezoneNoCycle timezone

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
total_issuesNo
cancelled_issuesNo
completed_issuesNo
started_issuesNo
unstarted_issuesNo
backlog_issuesNo
total_estimatesNo
completed_estimatesNo
started_estimatesNo
created_atNo
updated_atNo
deleted_atNo
nameYes
descriptionNo
start_dateNo
end_dateNo
view_propsNo
sort_orderNo
external_sourceNo
external_idNo
progress_snapshotNo
archived_atNo
logo_propsNo
timezoneNo
versionNo
created_byNo
updated_byNo
projectNo
workspaceNo
owned_byNo
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so description carries full burden. It only states 'Create a new cycle' without disclosing side effects, required permissions, or behavioral traits like data mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence is concise but fails to provide necessary details. It is under-specified, so not optimally sized for a tool with 9 parameters.

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?

Despite having an output schema, the description omits what the tool returns. With 9 parameters and no behavioral context, the description is insufficient for complete understanding.

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 coverage is 100% with parameter descriptions. Description adds no extra meaning beyond schema, so baseline 3 is appropriate.

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?

Description clearly states verb 'create' and resource 'cycle', making purpose obvious. However, it does not differentiate from sibling tools like 'create_milestone' or 'create_module', which follow the same pattern.

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?

No guidance on when to use this tool vs alternatives. No prerequisites, exclusions, or context provided. The description is a single sentence lacking usage instructions.

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/goto-software/plane-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server