Linear

linear_createProject

Create a new project in Linear by providing required team IDs and name. Optionally set lead, members, dates, status, and more for full control.

Instructions

Create a new 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": {
      "name": "<name>",
      "teamIds": "<teamIds>"
    },
    "name": "linear_createProject"
  }
}

Input Schema

Name	Required	Description
`icon`	No	Project icon
`name`	Yes	Name of the project
`color`	No	Project color
`state`	No	Initial project status by lifecycle type/name (e.g., 'planned', 'started') or project status UUID
`leadId`	No	ID of the project lead
`content`	No	Content of the project (Markdown supported)
`teamIds`	Yes	IDs of the teams this project belongs to
`memberIds`	No	IDs of users assigned as project members
`sortOrder`	No	Project sort order
`startDate`	No	Project start date
`targetDate`	No	Project target date
`description`	No	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": "Project color",
+  "type": "string"
+}

addedInput schema / properties / icon

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

addedInput schema / properties / leadId

Added value: +{
+  "description": "ID of the project lead",
+  "type": "string"
+}

addedInput schema / properties / memberIds

Added value: +{
+  "description": "IDs of users assigned as project members",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / sortOrder

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

addedInput schema / properties / startDate

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

changedInput schema / properties / state / description

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

addedInput schema / properties / targetDate

Added value: +{
+  "description": "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.8/5.0

Behavior2/5

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

Annotations already indicate readOnlyHint=false (modifying) and destructiveHint=false (not destructive), but the description adds no additional behavioral context, such as permissions required or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at 5 words, but lacks necessary elaboration. Could be more informative without being verbose.

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?

With 12 parameters and an output schema, the description is insufficient. It does not explain the tool's full capabilities, default behavior, or how the response is structured, despite the output schema existing.

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 baseline is 3. Description does not add any meaning beyond what is already in the schema (e.g., what each parameter does is already documented in the schema).

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 it creates a new project in Linear, which is a specific verb and resource. However, it does not differentiate from siblings like linear_updateProject or linear_archiveProject, but among the many tools, it is clear enough.

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 provided on when to use this tool vs. alternatives such as linear_updateProject or related project management tools. The description lacks context for appropriate usage.

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

Deploy Server