Clink MCP Server

update_project

Modify project details like title, description, slug, or color in the Clink MCP Server to keep project information current and accurate.

Instructions

Update a project's title, description, slug, or color.

    Args:
        project_id: The project ID
        title: New title (optional)
        description: New description (optional)
        slug: New slug (optional)
        color: New hex color (optional, e.g., "#3B82F6")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "update_project"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes
`title`	No
`description`	No
`slug`	No
`color`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jan 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't mention whether changes are reversible, what permissions are required, or how the system handles partial updates. It also doesn't describe the response format or any side effects, leaving significant behavioral gaps for a mutation tool.

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 efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence serves a purpose, and there's no redundant information. However, the formatting with indented 'Args:' section could be cleaner, and it could be more front-loaded with critical behavioral information.

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?

Given this is a mutation tool with 5 parameters, 0% schema description coverage, no annotations, but with an output schema, the description is moderately complete. It covers the basic purpose and parameters but lacks important context about permissions, side effects, and usage guidelines. The output schema helps with return values, but behavioral aspects remain underspecified.

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 description lists all 5 parameters and provides basic semantic context (e.g., 'color' expects a hex value like '#3B82F6'), which adds value beyond the schema's 0% description coverage. However, it doesn't explain constraints like slug format, title length limits, or what happens when optional parameters are omitted. The schema already defines types and optionality, so the description provides moderate additional meaning.

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 clearly states the action ('Update') and resource ('project') with specific fields that can be modified (title, description, slug, color). It distinguishes itself from sibling tools like 'create_project' by focusing on updates rather than creation. However, it doesn't explicitly differentiate from other update tools like 'update_checkpoint' or 'update_milestone'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like permissions needed, nor does it suggest when to use 'update_project' versus other update tools like 'update_checkpoint' or 'update_milestone'. The only implied usage is for modifying project attributes, but no explicit context is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.