Skip to main content
Glama

update_cycle

Idempotent

Update an existing cycle's details including name, dates, description, and owner by providing the cycle ID.

Instructions

Update a cycle by ID.

Args: workspace_slug: The workspace slug identifier project_id: UUID of the project cycle_id: UUID of the cycle name: Cycle name description: Cycle description start_date: Cycle start date (ISO 8601 format) end_date: Cycle end date (ISO 8601 format) owned_by: UUID of the user who owns the cycle external_source: External system source name external_id: External system identifier timezone: Cycle timezone

Returns: Updated Cycle object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
cycle_idYes
end_dateNo
owned_byNo
timezoneNo
project_idYes
start_dateNo
descriptionNo
external_idNo
external_sourceNo

Output Schema

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

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

Annotations indicate idempotent and non-destructive mutation. The description says 'Update' but does not provide additional behavioral details such as partial update capability, side effects, or permission requirements beyond what is obvious from the name.

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?

The description is structured as a docstring with an Args list, but it is verbose and includes redundant parameter listings that mirror the schema. Could be more concise by omitting obvious fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not shown) and annotations covering idempotency and safety, the description adequately explains parameter semantics and overall purpose. Missing error or edge-case information, but sufficient for a standard update tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The Args section adds meaningful context to each parameter (e.g., 'ISO 8601 format' for dates), which goes beyond the schema that only has types and defaults. With 0% schema coverage, the description fully compensates.

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 begins with 'Update a cycle by ID' which clearly states the action (update) and resource (cycle). It distinguishes from sibling tools like create, retrieve, delete, and complete by the verb, but does not explicitly differentiate.

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 versus alternatives like complete_cycle, or any prerequisites or context. The description only lists parameters without usage context.

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/Bl4nk44/plane-ce-mcp'

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