Skip to main content
Glama
10xtechnology

Linear MCP Server

linear_edit_issue

Updates specified fields on an existing issue, such as title, description, priority, assignee, labels, project, milestone, estimate, due date, parent, or sort order.

Instructions

Edit an existing issue, updating any of its fields. Note: When setting projectMilestoneId, you must also set projectId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesRequired: The UUID of the issue to update
titleNoThe issue title
descriptionNoThe issue description in markdown format
stateIdNoUUID of the target state
priorityNoIssue priority (0=No priority, 1=Urgent, 2=High, 3=Normal, 4=Low)
assigneeIdNoUUID of the user to assign the issue to
labelIdsNoArray of label UUIDs (replaces existing labels)
projectIdNoUUID of the project to associate with the issue
projectMilestoneIdNoUUID of the project milestone to associate with the issue. Note: Requires projectId to be set when using this field
estimateNoThe estimated complexity points for the issue
dueDateNoThe due date in YYYY-MM-DD format
parentIdNoUUID of the parent issue
sortOrderNoPosition of the issue relative to other issues
Behavior3/5

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

With no annotations, the description carries behavioral burden. It mentions the constraint but does not disclose other behaviors like whether updates are atomic, permissions required, or side effects. The schema provides some behavioral details (e.g., labelIds replaces existing), but the description adds little beyond the constraint.

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 plus a note. It is extremely concise, front-loaded, and contains no unnecessary words. Every part is useful.

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 13 parameters and no output schema, the description is minimal. It does not explain return values, error handling, or relationships beyond the noted constraint. The schema fills in details, but the description could provide more context for a complex update tool.

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 repeats the constraint from the schema for projectMilestoneId, but does not add new meaning beyond what the schema already provides.

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 clearly states the tool edits an existing issue and updates its fields. It distinguishes from sibling tools like linear_create_issue (create) and linear_delete_issue (delete) by implying 'edit' as the action.

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?

The description provides a specific constraint: when setting projectMilestoneId, projectId must also be set. This guides correct usage. However, it does not explicitly state when to use this tool versus alternatives like linear_create_issue or linear_bulk_update_issues, though the name and context suggest it is for single-issue updates.

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

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