Skip to main content
Glama
tacticlaunch

Linear

by tacticlaunch
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

linear_updateMilestone

Idempotent

Update an existing Linear project milestone by providing its ID and at least one field to change, such as name, description, or target date.

Instructions

Update an existing project milestone in Linear. Provide id plus at least one other field to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the milestone to update
nameNoUpdated name of the milestone
projectIdNoUpdated project ID for the milestone
sortOrderNoUpdated sort order for the milestone within its project
targetDateNoUpdated planned target date for the milestone (YYYY-MM-DD format)
descriptionNoUpdated milestone description in markdown format

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
statusNo
projectNo
progressNo
createdAtNo
sortOrderNo
updatedAtNo
archivedAtNo
targetDateNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.4.2
    • changedOutput schema / properties / progress / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / sortOrder / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
  2. Changed1 schema field changedv1.4.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "archivedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "progress": {
+      "type": "number"
+    },
+    "project": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "sortOrder": {
+      "type": "number"
+    },
+    "status": {
+      "type": "string"
+    },
+    "targetDate": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updatedAt": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Addedv1.1.2

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already convey non-read-only, non-destructive, idempotent behavior. The description adds that an update requires a value to change beyond the id, but does not discuss validation, auth, 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.

Conciseness5/5

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

A single sentence with no filler; the core requirement is front-loaded and immediately actionable.

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?

For a simple update operation, the description, full schema coverage, and annotations provide everything needed to invoke it correctly. The output schema covers return values, so no further description is required.

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?

The schema documents all parameters at 100% coverage, so the baseline is 3. The description adds the meaningful constraint that calling with only id is insufficient, which is not visible in the schema alone.

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?

States a specific verb ('Update') and resource ('existing project milestone'), making the tool's action unambiguous. It is clearly distinct from sibling tools like linear_createMilestone or linear_archiveMilestone because it says 'existing' and 'to change'.

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?

Gives a clear usage rule: provide id plus at least one other field to change. It does not explicitly name alternatives or exclusions, but the rule is enough to avoid invalid calls.

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/tacticlaunch/mcp-linear'

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