Skip to main content
Glama

update_project

Partially update a Kanboard project's attributes by specifying only the fields to change. Validation runs before any write, preventing partial or erroneous updates.

Instructions

Update the attributes of an existing Kanboard project (partial update). Only the fields you pass are changed; omitted fields keep their current values, and validation runs before any write, so an invalid call modifies nothing. At least one field besides 'project_id' must be provided — otherwise VALIDATION_ERROR. This tool updates project attributes only: to manage members use add_project_user / remove_project_user, to manage columns use create_column / move_column, and to delete a project use delete_project. Returns { ok: true, project_id } on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject id to update (required).
nameNoNew project name (1–255 chars).
descriptionNoNew project description.
identifierNoNew short identifier (e.g. 'PRJ'). Must be unique.
owner_idNoNew owner user id.
start_dateNoNew start date as ISO 8601 string, Unix epoch seconds (integer), or null to clear.
end_dateNoNew end date as ISO 8601 string, Unix epoch seconds (integer), or null to clear.
emailNoNew project notification email address.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses partial update behavior, pre-write validation, error condition, and return format. Lacks details on auth or rate limits but sufficient for a simple mutation.

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 concise (few sentences), front-loaded with verb and resource, and every sentence adds essential information without redundancy.

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

Completeness5/5

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

Given 8 parameters and no output schema, the description explains behavior, validation, error condition, and return format. It also provides context for related tools, making it complete for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline 3. The description adds value by explaining the partial update semantic (only passed fields change) and the requirement for at least one extra field, which is not explicit in schema.

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 clearly states it updates an existing Kanboard project (partial update). It distinguishes from sibling tools by explicitly mentioning that members, columns, and deletion are managed by other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It provides explicit when-to-use (update project attributes) and when-not-to-use (members, columns, delete) with named alternatives (add_project_user, create_column, delete_project). Also specifies the requirement of at least one field beyond project_id.

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