Skip to main content
Glama

linear_updateIssue

Modify existing Linear issues by updating fields like title, description, state, priority, assignee, labels, project, and due date. Keep issue tracking accurate with this tool.

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
descriptionNoNew description for the issue (Markdown supported)
stateIdNoID of the new state for the 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
projectMilestoneIdNoID of the project milestone to assign to the issue
assigneeIdNoID of the user to assign the issue to, or null to unassign
cycleIdNoID of the cycle to move the issue to, or null to remove from current cycle
estimateNoThe estimated complexity/points for the issue
dueDateNoThe new due date for the issue (YYYY-MM-DD format), or null to remove
labelIdsNoIDs of the labels to set on the issue (replacing existing labels)
addedLabelIdsNoIDs of labels to add to the issue (without removing existing ones)
removedLabelIdsNoIDs of labels to remove from the issue
parentIdNoID of the parent issue, or null to convert to a regular issue
subscriberIdsNoIDs of the users to subscribe to the issue (replacing existing subscribers)
teamIdNoID of the team to move the issue to
sortOrderNoThe position of the issue in relation to other issues
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as idempotency, partial update behavior, error states, or side effects. The tool clearly performs a mutation, but its specifics are undisclosed.

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?

Single sentence, no unnecessary words, directly states purpose.

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?

Tool has 18 parameters and no output schema or annotations. The description is too sparse to guide an agent on behavior, return values, or expected outcomes for complex updates.

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. The description adds no extra meaning beyond the schema; the schema already describes each parameter adequately.

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 states the action (update) and the target resource (existing issue), distinguishing it from creation, archiving, or retrieval tools.

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 other update-related tools (e.g., linear_updateIssueCustomField, linear_setIssuePriority). Lacks context about prerequisites or alternatives.

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