Plane MCP Server

Overview Schema Source Related Servers Discussions Admin

Create Page

create_page

Create a workspace wiki page or a project page with title, optional parent, color, access, lock, and HTML or plain-text body.

Instructions

Create a page — a workspace wiki page, or a page inside a project.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Page title.
`color`	No	Optional page color, e.g. "#ff4444".
`access`	No	"public" (default) or "private".	public
`is_locked`	No	Lock the page so it cannot be edited.
`parent_id`	No	Parent page UUID, to nest the page.
`project_id`	No	Project UUID to create a project page; omit for a workspace wiki page.
`description`	No	Plain-text body (converted to HTML for you).
`description_html`	No	HTML body; takes precedence over `description`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that a page is created and gives no information about permissions, side effects, locking behavior, access defaults, or what happens after creation. This is a meaningful gap for a mutation tool.

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 a single, focused sentence with no filler. It front-loads the core action and immediately conveys the key scope distinction.

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?

Although the tool has eight parameters, the schema describes each one completely, and an output schema exists. The description plus schema is largely sufficient for correct invocation; only richer behavioral caveats are missing.

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 description coverage is 100%, so the schema fully documents all eight parameters. The description adds only a high-level scope distinction and no additional parameter-level meaning, so the schema-heavy baseline of 3 is appropriate.

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 starts with a specific verb and resource ('Create a page') and immediately clarifies the two valid scopes: workspace wiki page or page inside a project. This clearly distinguishes it from sibling tools like create_project and create_work_item.

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 communicates the general context but does not explicitly say when to choose this tool over alternatives, nor does it provide exclusions or prerequisites. The workspace-vs-project distinction is present but only implied rather than framed as a decision rule.

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