Linear

by cline

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

linear_update_project_milestone

Update existing project milestones by modifying name, description, target date, project assignment, and sort order.

Instructions

Update an existing project milestone

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_update_project_milestone"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The ID of the project milestone to update
`name`	No	The name of the project milestone
`projectId`	No	The ID of the project this milestone belongs to
`sortOrder`	No	The sort order for the project milestone within a project
`targetDate`	No	The planned target date of the project milestone (ISO 8601 format)
`description`	No	The description of the project milestone in markdown format

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.3/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 for disclosing behavioral traits. It only states 'update an existing project milestone' without explaining whether fields are partially updated, whether permissions are required, or what the response contains. The behavior of omitted fields is unspecified, which is a significant gap for a mutation operation.

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 a single, front-loaded sentence that states the tool's purpose without any wasted words. It is highly concise and well-structured.

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?

The schema is rich and covers all parameters, but the description lacks essential behavioral context such as partial update semantics, required permissions, and return values. For a simple update tool with no output schema and no annotations, this is a minimal but viable description, though it leaves gaps in what the agent can expect.

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 input schema has 100% coverage with descriptions for all 6 parameters, so the schema already documents each parameter. The description adds no additional semantic meaning beyond what is in the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb 'update' with a clear resource 'existing project milestone', which clearly distinguishes it from sibling tools like create, delete, or get. The word 'existing' clarifies that it is a modification operation, not creation.

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 given for when to use this tool versus alternatives, such as creating a new milestone or deleting one. The description does not mention any context, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

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