Skip to main content
Glama

create_project

Create a new project in your workspace with specified name, identifier, and optional settings like lead, assignee, views, and archive rules.

Instructions

Create a new project.

Args: workspace_slug: The workspace slug identifier name: Project name identifier: Project identifier (e.g., "MP" for "My Project") description: Project description project_lead: UUID of the project lead user default_assignee: UUID of the default assignee user emoji: Emoji for the project cover_image: Cover image URL or asset ID module_view: Enable module view cycle_view: Enable cycle view issue_views_view: Enable issue views view page_view: Enable page view intake_view: Enable intake view guest_view_all_features: Allow guests to view all features archive_in: Days until auto-archive close_in: Days until auto-close timezone: Project timezone external_source: External system source name external_id: External system identifier is_issue_type_enabled: Enable issue types

Returns: Created Project object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
emojiNo
close_inNo
timezoneNo
page_viewNo
archive_inNo
cycle_viewNo
identifierYes
cover_imageNo
descriptionNo
external_idNo
intake_viewNo
module_viewNo
project_leadNo
external_sourceNo
default_assigneeNo
issue_views_viewNo
is_issue_type_enabledNo
guest_view_all_featuresNo

Output Schema

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

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

Annotations indicate writes (readOnlyHint false) but description does not disclose any additional behavioral traits (e.g., side effects, permissions, rate limits). Major inconsistency: description lists workspace_slug parameter not present in input schema, causing potential confusion.

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?

Structured as a list of arguments following a clear one-line purpose. Reasonably concise for 19 parameters, though could be slightly tighter.

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?

Covers purpose and parameters, but lacks context on side effects (openWorldHint true). Inconsistency with workspace_slug reduces completeness. Output schema exists so return description is acceptable.

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?

Description provides brief explanations for each parameter (e.g., 'Project identifier (e.g., MP for My Project)'), adding value over bare schema (0% coverage). However, workspace_slug is described but missing from schema, and defaults are not mentioned despite schema showing null defaults.

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?

Clearly states 'Create a new project' with specific verb and resource. Differentiates from sibling tools like update_project and delete_project by indicating creation.

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 vs alternatives. Does not mention prerequisites or context for selecting this tool over update_project or list_projects.

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/Bl4nk44/plane-ce-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server