Skip to main content
Glama
goto-software

plane-mcp-server

create_initiative

Add a new initiative to the workspace with name, optional dates, state, lead, and description.

Instructions

Create a new initiative in the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesInitiative name
description_htmlNoHTML description of the initiative
start_dateNoInitiative start date (ISO 8601 format)
end_dateNoInitiative end date (ISO 8601 format)
logo_propsNoLogo properties dictionary
stateNoInitiative state (DRAFT, PLANNED, ACTIVE, COMPLETED, CLOSED)
leadNoUUID of the user who leads the initiative

Output Schema

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

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

With no annotations, the description must carry the full burden. It only states the action without disclosing side effects, required permissions, or return behavior. The agent learns nothing beyond the basic operation.

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

Conciseness4/5

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

The description is a single, front-loaded sentence that is efficient. However, it is almost too brief, leaving out valuable context.

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 the simple create operation with well-documented parameters, the description is adequate but incomplete. It omits the return format, workspace context (beyond 'in the workspace'), and any preconditions.

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?

The input schema has 100% description coverage, so the schema already documents parameters. The description adds no extra meaning, resulting in a baseline score of 3.

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 'Create a new initiative in the workspace,' which matches the tool name. It is specific about the verb and resource, but it does not differentiate from sibling creation tools like create_project or create_cycle.

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 is provided on when to use this tool over other creation tools. The description lacks context about prerequisites or scenarios for creating an initiative.

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