Skip to main content
Glama
goto-software

plane-mcp-server

create_project

Create a new project by providing a name and identifier. Optionally configure views, assignees, and archiving rules.

Instructions

Create a new project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
identifierYesProject identifier (e.g., "MP" for "My Project")
descriptionNoProject description
project_leadNoUUID of the project lead user
default_assigneeNoUUID of the default assignee user
emojiNoEmoji for the project
cover_imageNoCover image URL or asset ID
module_viewNoEnable module view
cycle_viewNoEnable cycle view
issue_views_viewNoEnable issue views view
page_viewNoEnable page view
intake_viewNoEnable intake view
guest_view_all_featuresNoAllow guests to view all features
archive_inNoDays until auto-archive
close_inNoDays until auto-close
timezoneNoProject timezone
external_sourceNoExternal system source name
external_idNoExternal system identifier
is_issue_type_enabledNoEnable issue types

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
total_membersNo
total_cyclesNo
total_modulesNo
is_memberNo
sort_orderNo
member_roleNo
is_deployedNo
cover_image_urlNo
created_atNo
updated_atNo
deleted_atNo
nameYes
descriptionNo
description_textNo
description_htmlNo
networkNo
identifierYes
emojiNo
icon_propNo
module_viewNo
cycle_viewNo
issue_views_viewNo
page_viewNo
intake_viewNo
is_time_tracking_enabledNo
is_issue_type_enabledNo
guest_view_all_featuresNo
cover_imageNo
archive_inNo
close_inNo
logo_propsNo
archived_atNo
timezoneNo
external_sourceNo
external_idNo
created_byNo
updated_byNo
workspaceNo
default_assigneeNo
project_leadNo
cover_image_assetNo
estimateNo
default_stateNo
Behavior2/5

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

The description only states 'Create' which indicates mutation, but no details on side effects, permissions, or return behavior. Annotations are absent, and the description fails to disclose any behavioral traits beyond the obvious creation action.

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 extremely concise, consisting of a single sentence. It is front-loaded and efficient, but it may be too terse, lacking helpful context that could be included without significant bloat.

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 complexity (19 parameters) and the presence of an output schema, the description is incomplete. It does not mention that the tool returns the created project, nor does it provide error handling or constraints. The description should offer more context for effective tool usage.

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 already documents all parameters. The description adds no additional meaning beyond the schema, meeting the baseline of 3 per guidelines.

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?

Description clearly states 'Create a new project' with a specific verb and resource. However, among many sibling create tools (create_cycle, create_epic, etc.), it does not explicitly differentiate the purpose of creating a project versus other entities.

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 versus alternative creation tools (e.g., create_epic, create_cycle). There is no mention of prerequisites, context, or when not to use it.

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