Skip to main content
Glama

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 handler function that executes the linear_updateIssue tool. It validates the input arguments using the isUpdateIssueArgs type guard and calls the LinearService.updateIssue method to perform the update.
    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 schema definition for the linear_updateIssue tool, specifying input and output schemas used for validation.
    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' },
        },
      },
    };
  • Registration of the linear_updateIssue tool handler in the registerToolHandlers function, mapping the tool name to the handleUpdateIssue handler.
    linear_updateIssue: handleUpdateIssue(linearService),
  • Type guard function isUpdateIssueArgs used by the handler to validate input arguments against the expected schema.
     * 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')
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Update' implies mutation, the description doesn't mention permission requirements, whether changes are reversible, how partial updates are handled, or what the response contains. For a mutation tool with 17 parameters and no annotation coverage, this leaves significant behavioral questions unanswered.

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 unnecessary words. It's appropriately sized and front-loaded, with every word earning its place in conveying the essential information.

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 complex mutation tool with 17 parameters, no annotations, and no output schema, the description is insufficient. It doesn't address behavioral aspects like permissions, side effects, or response format, nor does it provide usage guidance relative to many specialized sibling tools. The description relies entirely on the schema for parameter documentation but fails to complement it with necessary context.

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 description coverage is 100%, so the schema already documents all 17 parameters thoroughly with clear descriptions and formats. The description adds no additional parameter information beyond what's in the schema, which 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 action ('Update') and resource ('an existing issue in Linear'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling update tools like linear_updateInitiative or linear_updateProject, which would require mentioning it specifically handles issue updates rather than other entity types.

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 like linear_assignIssue, linear_setIssuePriority, linear_transferIssue, and linear_updateInitiative, there's no indication of when this comprehensive update tool is preferable over more specialized ones or what prerequisites might exist.

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