Skip to main content
Glama
goto-software

plane-mcp-server

create_project_page

Create a project page by providing a name and HTML content, with optional settings for access, color, lock status, and external references.

Instructions

Create a project page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
nameYesPage name
description_htmlYesPage content in HTML format
accessNoAccess level for the page (integer)
colorNoPage color
is_lockedNoWhether the page is locked
archived_atNoArchive timestamp (ISO 8601 format)
view_propsNoView properties dictionary
logo_propsNoLogo properties dictionary
external_idNoExternal system identifier
external_sourceNoExternal system source name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
description_strippedNo
description_htmlNo
description_binaryNo
descriptionNo
created_atNo
updated_atNo
owned_byNo
anchorNo
workspaceNo
projectsNo
Behavior2/5

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

No annotations are provided, so the description carries full burden. It offers no behavioral details about side effects, permissions, or response behavior beyond creation itself.

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 very short and concise, but lacks structure or front-loading of key information. It is not verbose, but also not particularly helpful.

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

Completeness2/5

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

Given the tool has 11 parameters and no annotations, the description is too brief to be complete. It does not explain the page's role within a project, relationships, or expected behavior.

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 schema has 100% parameter description coverage, so the tool description adds no extra meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 states 'Create a project page.' which clearly indicates a verb and resource. However, it does not differentiate from sibling tool 'create_workspace_page', making its scope less precise.

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 'create_workspace_page'. The description lacks any usage context or prerequisites.

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