Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_updateIssue

Modify existing Linear issues by updating titles, descriptions, priorities, assignees, due dates, labels, and other project management fields to reflect current status and requirements.

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
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

Implementation Reference

  • The main handler function for the linear_updateIssue tool. It validates the input arguments using the type guard and delegates the update logic to the LinearService.
    export function handleUpdateIssue(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isUpdateIssueArgs(args)) {
            throw new Error("Invalid arguments for updateIssue");
          }
          
          return await linearService.updateIssue(args);
        } catch (error) {
          logError("Error updating issue", error);
          throw error;
        }
      };
    }
  • The MCP tool schema definition for linear_updateIssue, including input and output schemas.
    export const updateIssueToolDefinition: MCPToolDefinition = {
      name: "linear_updateIssue",
      description: "Update an existing issue in Linear",
      input_schema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "ID or identifier of the issue to update (e.g., ABC-123)",
          },
          title: {
            type: "string",
            description: "New title for the issue",
          },
          description: {
            type: "string",
            description: "New description for the issue (Markdown supported)",
          },
          stateId: {
            type: "string",
            description: "ID of the new state for the issue",
          },
          priority: {
            type: "number",
            description: "New priority for the issue (0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low)",
          },
          projectId: {
            type: "string",
            description: "ID of the project to move the issue to",
          },
          assigneeId: {
            type: "string",
            description: "ID of the user to assign the issue to, or null to unassign",
          },
          cycleId: {
            type: "string",
            description: "ID of the cycle to move the issue to, or null to remove from current cycle",
          },
          estimate: {
            type: "number",
            description: "The estimated complexity/points for the issue",
          },
          dueDate: {
            type: "string",
            description: "The new due date for the issue (YYYY-MM-DD format), or null to remove",
          },
          labelIds: {
            type: "array",
            items: { type: "string" },
            description: "IDs of the labels to set on the issue (replacing existing labels)",
          },
          addedLabelIds: {
            type: "array",
            items: { type: "string" },
            description: "IDs of labels to add to the issue (without removing existing ones)",
          },
          removedLabelIds: {
            type: "array",
            items: { type: "string" },
            description: "IDs of labels to remove from the issue",
          },
          parentId: {
            type: "string",
            description: "ID of the parent issue, or null to convert to a regular issue",
          },
          subscriberIds: {
            type: "array",
            items: { type: "string" },
            description: "IDs of the users to subscribe to the issue (replacing existing subscribers)",
          },
          teamId: {
            type: "string",
            description: "ID of the team to move the issue to",
          },
          sortOrder: {
            type: "number",
            description: "The position of the issue in relation to other issues",
          },
        },
        required: ["id"],
      },
      output_schema: {
        type: "object",
        properties: {
          id: { type: "string" },
          identifier: { type: "string" },
          title: { type: "string" },
          url: { type: "string" }
        }
      }
    };
  • The registration of the linear_updateIssue handler in the tool handlers map, mapping the tool name to the handleUpdateIssue function.
    export function registerToolHandlers(linearService: LinearService) {
      return {
        // User tools
        linear_getViewer: handleGetViewer(linearService),
        linear_getOrganization: handleGetOrganization(linearService),
        linear_getUsers: handleGetUsers(linearService),
        linear_getLabels: handleGetLabels(linearService),
    
        // Team tools
        linear_getTeams: handleGetTeams(linearService),
        linear_getWorkflowStates: handleGetWorkflowStates(linearService),
    
        // Project tools
        linear_getProjects: handleGetProjects(linearService),
        linear_createProject: handleCreateProject(linearService),
        
        // Project Management tools
        linear_updateProject: handleUpdateProject(linearService),
        linear_addIssueToProject: handleAddIssueToProject(linearService),
        linear_getProjectIssues: handleGetProjectIssues(linearService),
        
        // Cycle Management tools
        linear_getCycles: handleGetCycles(linearService),
        linear_getActiveCycle: handleGetActiveCycle(linearService),
        linear_addIssueToCycle: handleAddIssueToCycle(linearService),
    
        // Issue tools
        linear_getIssues: handleGetIssues(linearService),
        linear_getIssueById: handleGetIssueById(linearService),
        linear_searchIssues: handleSearchIssues(linearService),
        linear_createIssue: handleCreateIssue(linearService),
        linear_updateIssue: handleUpdateIssue(linearService),
        linear_createComment: handleCreateComment(linearService),
        linear_addIssueLabel: handleAddIssueLabel(linearService),
        linear_removeIssueLabel: handleRemoveIssueLabel(linearService),
        
        // New Issue Management tools
        linear_assignIssue: handleAssignIssue(linearService),
        linear_subscribeToIssue: handleSubscribeToIssue(linearService),
        linear_convertIssueToSubtask: handleConvertIssueToSubtask(linearService),
        linear_createIssueRelation: handleCreateIssueRelation(linearService),
        linear_archiveIssue: handleArchiveIssue(linearService),
        linear_setIssuePriority: handleSetIssuePriority(linearService),
        linear_transferIssue: handleTransferIssue(linearService),
        linear_duplicateIssue: handleDuplicateIssue(linearService),
        linear_getIssueHistory: handleGetIssueHistory(linearService),
        
        // Comment Management tools
        linear_getComments: handleGetComments(linearService)
      };
  • Type guard function for validating arguments to the linear_updateIssue tool.
     * Type guard for linear_updateIssue tool arguments
     */
    export function isUpdateIssueArgs(args: unknown): args is {
      id: string;
      title?: string;
      description?: string;
      stateId?: string;
      priority?: number;
      projectId?: string;
      assigneeId?: string;
      cycleId?: string;
      estimate?: number;
      dueDate?: string;
      labelIds?: string[];
      addedLabelIds?: string[];
      removedLabelIds?: string[];
      parentId?: string;
      subscriberIds?: string[];
      teamId?: string;
      sortOrder?: number;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "id" in args &&
        typeof (args as { id: string }).id === "string" &&
        (!("title" in args) || typeof (args as { title: string }).title === "string") &&
        (!("description" in args) || typeof (args as { description: string }).description === "string") &&
        (!("stateId" in args) || typeof (args as { stateId: string }).stateId === "string") &&
        (!("priority" in args) || typeof (args as { priority: number }).priority === "number") &&
        (!("projectId" in args) || typeof (args as { projectId: string }).projectId === "string") &&
        (!("assigneeId" in args) || typeof (args as { assigneeId: string }).assigneeId === "string") &&
        (!("cycleId" in args) || typeof (args as { cycleId: string }).cycleId === "string") &&
        (!("estimate" in args) || typeof (args as { estimate: number }).estimate === "number") &&
        (!("dueDate" in args) || typeof (args as { dueDate: string }).dueDate === "string") &&
        (!("labelIds" in args) || Array.isArray((args as { labelIds: string[] }).labelIds)) &&
        (!("addedLabelIds" in args) || Array.isArray((args as { addedLabelIds: string[] }).addedLabelIds)) &&
        (!("removedLabelIds" in args) || Array.isArray((args as { removedLabelIds: string[] }).removedLabelIds)) &&
        (!("parentId" in args) || typeof (args as { parentId: string }).parentId === "string") &&
        (!("subscriberIds" in args) || Array.isArray((args as { subscriberIds: string[] }).subscriberIds)) &&
        (!("teamId" in args) || typeof (args as { teamId: string }).teamId === "string") &&
        (!("sortOrder" in args) || typeof (args as { sortOrder: number }).sortOrder === "number")
      );
    }
  • The LinearService method that performs the actual API call to update the issue using the Linear SDK.
    async updateIssue(args: {
      id: string;
      title?: string;
      description?: string;
      stateId?: string;
      priority?: number;
      projectId?: string;
      assigneeId?: string;
      cycleId?: string;
      estimate?: number;
      dueDate?: string;
      labelIds?: string[];
      addedLabelIds?: string[];
      removedLabelIds?: string[];
      parentId?: string;
      subscriberIds?: string[];
      teamId?: string;
      sortOrder?: number;
    }) {
      const updatedIssue = await this.client.updateIssue(args.id, {
        title: args.title,
        description: args.description,
        stateId: args.stateId,
        priority: args.priority,
        projectId: args.projectId,
        assigneeId: args.assigneeId,
        cycleId: args.cycleId,
        estimate: args.estimate,
        dueDate: args.dueDate,
        labelIds: args.labelIds,
        addedLabelIds: args.addedLabelIds,
        removedLabelIds: args.removedLabelIds,
        parentId: args.parentId,
        subscriberIds: args.subscriberIds,
        teamId: args.teamId,
        sortOrder: args.sortOrder,
      });
    
      if (updatedIssue.success && updatedIssue.issue) {
        const issueData = await updatedIssue.issue;
        return {
          id: issueData.id,
          title: issueData.title,
          description: issueData.description,
          url: issueData.url,
        };
      } else {
        throw new Error('Failed to update issue');
      }
    }
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 of behavioral disclosure. While 'Update' implies a mutation operation, the description doesn't address important behavioral aspects: what permissions are required, whether updates are reversible, how partial updates are handled, what happens to unspecified fields, or what the response looks like. For a mutation tool with 17 parameters and no annotations, this is a significant gap.

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, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for what it communicates and gets straight to the point with no unnecessary elaboration.

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?

For a mutation tool with 17 parameters, no annotations, and no output schema, the description is inadequate. It doesn't address behavioral implications, error conditions, permissions, or what happens when the tool succeeds. Given the complexity and lack of structured metadata, the description should provide more context about how this update operation works in practice.

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 schema description coverage is 100%, so the schema already documents all 17 parameters thoroughly with clear descriptions, including format specifications and special values. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline expectation when schema coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Update') and resource ('an existing issue in Linear'), making the purpose immediately understandable. It distinguishes this from creation tools like 'linear_createIssue' by specifying 'existing issue', but doesn't explicitly differentiate from other update-related siblings like 'linear_updateProject' or 'linear_setIssuePriority'.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools that perform specific updates (like linear_setIssuePriority, linear_assignIssue, linear_addIssueToCycle), there's no indication whether this comprehensive update tool should be preferred over those specialized tools, or what the trade-offs might be.

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

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