Plane MCP Server

list_initiatives

Retrieve all initiatives in a Plane workspace, with support for pagination via query parameters.

Instructions

List all initiatives in a workspace.

Args: params: Optional query parameters as a dictionary (e.g., per_page, cursor)

Returns: List of Initiative objects

Raises: ToolError: if the initiatives feature is disabled. When disabled, initiatives are "Initiative" work items — the error gives the steps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_initiatives"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the ToolError for the disabled feature and mentions the pagination-related params (per_page, cursor), but it does not clarify whether 'all' requires iterative pagination or what the response shape is beyond 'List of Initiative objects' (though an output schema exists).

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 compact and well-structured with clear Args, Returns, and Raises sections. Every sentence adds value, and the error explanation is brief but useful. There is no fluff.

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 simple parameter set (one optional dict) and the presence of an output schema, the description covers purpose, parameters, return type, and an error condition. It could mention pagination behavior more explicitly, but the examples of per_page/cursor hint at it, making it sufficiently complete.

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 no descriptions (0% coverage), so the description's 'Optional query parameters as a dictionary (e.g., per_page, cursor)' adds needed semantics. However, it only gives two examples and does not enumerate possible keys, leaving the full parameter space vague.

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?

The description states 'List all initiatives in a workspace' with a clear verb and resource. It distinguishes from siblings like retrieve_initiative (single item) and list_initiative_projects (different resource), and the scope is explicit.

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?

The description gives clear context (list all initiatives in a workspace) and even notes the disabled-feature error, but it does not explicitly mention when to use this tool versus alternatives like list_projects or search_work_items. Usage is implied rather than directly contrasted with siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server