Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_setIssuePriority

Set priority levels for Linear issues to organize tasks by urgency, using numeric values from 0 (No priority) to 4 (Low).

Instructions

Set the priority of an issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesID or identifier of the issue (e.g., ABC-123)
priorityYesPriority level (0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low)

Implementation Reference

  • The handler function that implements the core logic for the linear_setIssuePriority tool. It performs input validation using a type guard and calls the LinearService to update the issue's priority.
    /**
     * Handler for setting issue priority
     */
    export function handleSetIssuePriority(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isSetIssuePriorityArgs(args)) {
            throw new Error("Invalid arguments for setIssuePriority");
          }
          
          return await linearService.setIssuePriority(args.issueId, args.priority);
        } catch (error) {
          logError("Error setting issue priority", error);
          throw error;
        }
      };
    }
  • The schema definition for the linear_setIssuePriority tool, specifying input parameters (issueId and priority) and output structure.
    export const setIssuePriorityToolDefinition: MCPToolDefinition = {
      name: "linear_setIssuePriority",
      description: "Set the priority of an issue",
      input_schema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "ID or identifier of the issue (e.g., ABC-123)",
          },
          priority: {
            type: "number",
            description: "Priority level (0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low)",
            enum: [0, 1, 2, 3, 4]
          },
        },
        required: ["issueId", "priority"],
      },
      output_schema: {
        type: "object",
        properties: {
          success: { type: "boolean" },
          issue: {
            type: "object",
            properties: {
              id: { type: "string" },
              identifier: { type: "string" },
              title: { type: "string" },
              priority: { type: "number" },
              url: { type: "string" }
            }
          }
        }
      }
    };
  • The registration of the tool handler 'handleSetIssuePriority' under the name 'linear_setIssuePriority' in the tool handlers registry.
    linear_setIssuePriority: handleSetIssuePriority(linearService),
  • Type guard function used by the handler to validate input arguments for the linear_setIssuePriority tool.
     * Type guard for linear_setIssuePriority tool arguments
     */
    export function isSetIssuePriorityArgs(args: unknown): args is {
      issueId: string;
      priority: number;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "issueId" in args &&
        typeof (args as { issueId: string }).issueId === "string" &&
        "priority" in args &&
        typeof (args as { priority: number }).priority === "number" &&
        [0, 1, 2, 3, 4].includes((args as { priority: number }).priority)
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Set the priority' implies a mutation operation, but it doesn't mention required permissions, whether this action is reversible, what happens to existing priority values, or any rate limits. For a mutation tool with zero 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 functionality without any wasted words. It's appropriately sized for a simple mutation tool and gets straight to the point.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what happens after setting the priority (success/failure indicators, return values), doesn't mention permissions or side effects, and doesn't differentiate from similar tools. Given the complexity of issue management systems, more context is needed.

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%, with both parameters clearly documented in the schema (issueId format and priority enum values). The description adds no additional parameter information beyond what's already in the structured schema, so it meets but doesn't exceed the baseline expectation.

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 ('Set') and resource ('priority of an issue'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar mutation tools like linear_updateIssue or linear_assignIssue, which could also affect issue properties.

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 siblings like linear_updateIssue (which likely handles multiple fields) and linear_assignIssue (which might handle assignments), there's no indication whether this tool is specialized for priority changes only or when it should be preferred over broader update tools.

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