Linear

linear_updateProject

Idempotent

Update an existing Linear project by changing its name, status, dates, lead, members, content, or other fields. Specify the project ID and any fields to modify.

Instructions

Update an existing project in Linear

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": {
      "id": "<id>"
    },
    "name": "linear_updateProject"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	ID of the project to update
`icon`	No	New project icon
`name`	No	New name of the project
`color`	No	New project color
`state`	No	New project status by lifecycle type/name (e.g., 'planned', 'started') or project status UUID
`leadId`	No	New project lead user ID
`content`	No	New content of the project (Markdown supported)
`memberIds`	No	Replacement list of project member user IDs
`sortOrder`	No	New project sort order
`startDate`	No	New project start date
`targetDate`	No	New project target date
`description`	No	New short summary of the project

Output Schema

Name	Required	Description	Default
`id`	No
`url`	No
`icon`	No
`lead`	No
`name`	No
`color`	No
`state`	No
`teams`	No
`content`	No
`trashed`	No
`startDate`	No
`targetDate`	No
`description`	No
`slackChannelId`	No
`microsoftTeamsChannelId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.4.1Jul 30, 2026

addedInput schema / properties / color

Added value: +{
+  "description": "New project color",
+  "type": "string"
+}

addedInput schema / properties / icon

Added value: +{
+  "description": "New project icon",
+  "type": "string"
+}

addedInput schema / properties / leadId

Added value: +{
+  "description": "New project lead user ID",
+  "type": "string"
+}

addedInput schema / properties / memberIds

Added value: +{
+  "description": "Replacement list of project member user IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / sortOrder

Added value: +{
+  "description": "New project sort order",
+  "type": "number"
+}

addedInput schema / properties / startDate

Added value: +{
+  "description": "New project start date",
+  "type": "string"
+}

changedInput schema / properties / state / description

Previous value: -"New state of the project (e.g., 'planned', 'started', 'paused', 'completed', 'canceled')"New value: +"New project status by lifecycle type/name (e.g., 'planned', 'started') or project status UUID"

addedInput schema / properties / targetDate

Added value: +{
+  "description": "New project target date",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "color": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "content": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "icon": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "lead": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "microsoftTeamsChannelId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "slackChannelId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "startDate": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "targetDate": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "teams": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "trashed": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedAug 18, 2025

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare idempotentHint=true, which aligns with 'update'. The description adds no behavioral context beyond what annotations provide, such as side effects, authorization needs, or error handling.

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 a single, front-loaded sentence with no wasted words. It is efficient but could be slightly more informative without losing conciseness.

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?

For a mutation tool with 12 parameters and no explicit explanation of side effects or return value (though output schema exists), the description is too brief. It lacks completeness for complex 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 coverage is 100%, so the input schema provides detailed parameter descriptions. The description does not add any additional meaning beyond 'update an existing project', which is baseline for high coverage.

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 the resource ('an existing project in Linear'). However, it does not distinguish this tool from siblings like linear_archiveProject or linear_createProject, which are also project-related actions.

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 alternatives (e.g., linear_archiveProject, linear_createProject). There is no mention of prerequisites or context.

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

Deploy Server