Skip to main content
Glama

update_initiative

Idempotent

Update an initiative by its ID to modify its name, description, dates, state, or lead. Manage initiative attributes efficiently.

Instructions

Update an initiative by ID.

Args: initiative_id: UUID of the initiative name: Initiative name description_html: HTML description of the initiative start_date: Initiative start date (ISO 8601 format) end_date: Initiative end date (ISO 8601 format) logo_props: Logo properties dictionary state: Initiative state (DRAFT, PLANNED, ACTIVE, COMPLETED, CLOSED) lead: UUID of the user who leads the initiative

Returns: Updated Initiative object

Raises: ToolError: if the initiatives feature is disabled. When disabled, the initiative is an "Initiative" work item - the error gives the steps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leadNo
nameNo
stateNo
end_dateNo
logo_propsNo
start_dateNo
initiative_idYes
description_htmlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
leadNo
nameYes
stateNo
end_dateNo
workspaceYes
created_atNo
deleted_atNo
logo_propsYes
start_dateNo
updated_atNo
descriptionNo
description_htmlNo
description_binaryNo
description_strippedNo
Behavior3/5

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

Annotations already indicate idempotent (idempotentHint: true) and non-destructive (destructiveHint: false). Description adds error behavior when feature disabled, but lacks details on permissions or side effects. Adequate but not rich.

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?

Structured as parameter list with returns and raises, front-loading purpose. Somewhat verbose with full parameter list repeated from schema. Adequate but could be more concise.

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

Completeness3/5

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

Given annotations and output schema, description covers purpose, parameters, and errors. Lacks usage context and deeper behavioral details. Fairly complete for a mutation tool but not exhaustive.

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?

Lists all parameters with names and types, adds format info (ISO 8601 for dates). However, schema coverage is 0% and description does not explain semantics beyond what is in the schema, e.g., logo_props structure is unclear. Baseline 3 due to low coverage and superficial help.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Explicitly states 'Update an initiative by ID', which clearly conveys the action and resource. Distinguishes from siblings like create_initiative, retrieve_initiative, and delete_initiative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use or when not to use. Context implied by name and sibling tools, but lacks clear comparisons or prerequisites, which is a gap given many sibling tools.

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