Skip to main content
Glama

create_project

Create a new Kanboard project by providing a required name and optional details like description, owner, dates, and email. Returns the project ID.

Instructions

Create a new Kanboard project. Requires a name (1–255 chars). Optionally provide a description, short identifier, owner user id, start_date / end_date (ISO 8601 string or epoch seconds), and email. After creating, adjust the board with create_column / create_swimlane, add members with add_project_user, and edit attributes with update_project. Returns { project_id } on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name (1–255 characters, required).
descriptionNoOptional project description.
identifierNoOptional short identifier (e.g. 'PRJ'). Must be unique across projects.
owner_idNoOptional numeric user id of the project owner.
start_dateNoOptional start date as ISO 8601 string or Unix epoch seconds (integer).
end_dateNoOptional end date as ISO 8601 string or Unix epoch seconds (integer).
emailNoOptional project notification email address.
Behavior4/5

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

No annotations provided, so description carries the burden. Discloses return value shape and re-iterates required constraints. Lacks side effects or permission details, but sufficient for a creation 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?

Three sentences, no fluff. Purpose, optional params, post-creation actions, and return value each get a sentence. Highly efficient.

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?

Covers creation and subsequent steps. Return value is specified. No output schema, but shape is simple. Adequate for the tool's complexity.

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 baseline 3. Description adds grouping of optional params and mentions the name length constraint already in schema. Marginal added value.

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 Kanboard project.' with specific verb and resource. Distinct from sibling tools that create 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear post-creation steps (use create_column, etc.), guiding the agent on workflow. Does not explicitly state when not to use, but context is adequate.

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/ErnestoCorona/kanboard-mcp'

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