Skip to main content
Glama

linear_updateIssue

Idempotent

Update any property of a Linear issue, including title, description, assignee, priority, state, labels, and due date.

Instructions

Update an existing issue in Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID or identifier of the issue to update (e.g., ABC-123)
titleNoNew title for the issue
teamIdNoID of the team to move the issue to
cycleIdNoID of the cycle to move the issue to, or null to remove from current cycle
dueDateNoThe new due date for the issue (YYYY-MM-DD format), or null to remove
stateIdNoID of the new state for the issue
estimateNoThe estimated complexity/points for the issue
labelIdsNoIDs of the labels to set on the issue (replacing existing labels)
parentIdNoID of the parent issue, or null to convert to a regular issue
priorityNoNew priority for the issue (0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low)
projectIdNoID of the project to move the issue to
sortOrderNoThe position of the issue in relation to other issues
assigneeIdNoID of the user to assign the issue to, or null to unassign
descriptionNoNew description for the issue (Markdown supported)
addedLabelIdsNoIDs of labels to add to the issue (without removing existing ones)
subscriberIdsNoIDs of the users to subscribe to the issue (replacing existing subscribers)
removedLabelIdsNoIDs of labels to remove from the issue
projectMilestoneIdNoID of the project milestone to assign to the issue

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
titleNo
identifierNo
Behavior3/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so description need not repeat these. However, it adds no extra behavioral details like permission requirements or side effects. The description is minimal but not contradictory.

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 sentence that is front-loaded with the verb and resource. Every word is necessary; no fluff.

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 the complexity (18 parameters) and the presence of an output schema, the description is very minimal. It does not mention typical use cases, interactions between parameters, or how the output looks. More context would be helpful.

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%, with all 18 parameters described in the input schema. The description does not add extra meaning beyond what is already in the schema, so a 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 'Update an existing issue in Linear' clearly specifies the verb (update) and resource (existing issue). It effectively distinguishes from sibling tools like createIssue, archiveIssue, or duplicateIssue.

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 on when to use this tool versus alternatives such as createIssue, assignIssue, or archiveIssue. The description lacks context about prerequisites or scenarios where update is appropriate.

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