Skip to main content
Glama
tiovikram

Linear MCP Server

by tiovikram

update_issue

Modify Linear issues by updating title, description, status, assignee, or priority to keep project tracking current.

Instructions

Update an existing issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesIssue ID
titleNoNew title (optional)
descriptionNoNew description (optional)
statusNoNew status (optional)
assigneeIdNoNew assignee ID (optional)
priorityNoNew priority (0-4, optional)

Implementation Reference

  • The main handler for the 'update_issue' tool. It validates the issueId, fetches the issue using LinearClient, applies the provided updates (title, description, status, assignee, priority), and returns the updated issue as JSON.
    case "update_issue": {
      const args = request.params.arguments as unknown as UpdateIssueArgs;
      if (!args?.issueId) {
        throw new Error("Issue ID is required");
      }
    
      const issue = await linearClient.issue(args.issueId);
      if (!issue) {
        throw new Error(`Issue ${args.issueId} not found`);
      }
    
      const updatedIssue = await issue.update({
        title: args.title,
        description: args.description,
        stateId: args.status,
        assigneeId: args.assigneeId,
        priority: args.priority,
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(updatedIssue, null, 2),
          },
        ],
      };
    }
  • TypeScript type definition for the input arguments of the 'update_issue' tool.
    type UpdateIssueArgs = {
      issueId: string;
      title?: string;
      description?: string;
      status?: string;
      assigneeId?: string;
      priority?: number;
    };
  • src/index.ts:125-160 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema for 'update_issue'.
    {
      name: "update_issue",
      description: "Update an existing issue",
      inputSchema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "Issue ID",
          },
          title: {
            type: "string",
            description: "New title (optional)",
          },
          description: {
            type: "string",
            description: "New description (optional)",
          },
          status: {
            type: "string",
            description: "New status (optional)",
          },
          assigneeId: {
            type: "string",
            description: "New assignee ID (optional)",
          },
          priority: {
            type: "number",
            description: "New priority (0-4, optional)",
            minimum: 0,
            maximum: 4,
          },
        },
        required: ["issueId"],
      },
    },
  • src/index.ts:49-49 (registration)
    Capability declaration enabling the 'update_issue' tool in the MCP server capabilities.
    update_issue: true,
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. It states 'Update an existing issue,' implying a mutation operation, but doesn't specify permissions required, whether changes are reversible, rate limits, or error handling. This leaves significant gaps in understanding the tool's behavior and risks.

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, direct sentence with zero wasted words: 'Update an existing issue.' It's front-loaded and efficiently conveys the core action without unnecessary elaboration, making it highly concise and well-structured.

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?

Given the tool's complexity as a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits, error cases, or what the update returns, leaving the agent under-informed about how to handle this operation effectively.

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 input schema has 100% description coverage, detailing all 6 parameters (e.g., 'issueId' as required, 'title' as optional). The description adds no additional meaning beyond the schema, such as explaining parameter interactions or constraints. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Update an existing issue' clearly states the action (update) and resource (issue), but it's vague about what aspects can be updated and doesn't distinguish it from sibling tools like 'create_issue' or 'get_issue'. It provides a basic purpose but lacks specificity about the scope of updates.

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 offers no guidance on when to use this tool versus alternatives such as 'create_issue' for new issues or 'get_issue' for viewing. It doesn't mention prerequisites like needing an existing issue ID or context for when updates are appropriate, leaving the agent without usage direction.

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

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