Skip to main content
Glama

linear_setIssuePriority

Set priority levels for Linear issues to manage workflow and focus on critical tasks. Use numeric values from 0 (No priority) to 4 (Low) to organize project management.

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 main handler function for the linear_setIssuePriority tool. It validates the input arguments using a type guard and delegates the actual priority update to the LinearService.
    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 tool schema definition including input and output schemas for linear_setIssuePriority.
    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' },
            },
          },
        },
      },
    };
  • Registration of the tool handler in the registerToolHandlers function.
    linear_setIssuePriority: handleSetIssuePriority(linearService),
  • Type guard function for validating the input arguments of linear_setIssuePriority.
     * 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)
      );
    }
  • The LinearService method that performs the actual API call to update the issue priority using the Linear SDK.
    async setIssuePriority(issueId: string, priority: number) {
      try {
        // Get the issue
        const issue = await this.client.issue(issueId);
        if (!issue) {
          throw new Error(`Issue with ID ${issueId} not found`);
        }
    
        // Update the issue priority
        await issue.update({
          priority: priority,
        });
    
        // Get the updated issue
        const updatedIssue = await this.client.issue(issue.id);
    
        return {
          success: true,
          issue: {
            id: updatedIssue.id,
            identifier: updatedIssue.identifier,
            title: updatedIssue.title,
            priority: updatedIssue.priority,
            url: updatedIssue.url,
          },
        };
      } catch (error) {
        console.error('Error setting issue priority:', error);
        throw error;
      }
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this requires specific permissions, whether it's idempotent, what happens on invalid inputs, or any rate limits. 'Set' implies mutation, but no further context is given, leaving gaps in understanding the tool's behavior.

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 waste. It's front-loaded and appropriately sized for the tool's purpose, making it easy to parse without 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?

Given no annotations and no output schema, the description is incomplete for a mutation tool. It lacks details on permissions, error handling, return values, or how it fits within the sibling toolset. For a 2-parameter tool with 100% schema coverage, more behavioral context is needed to be fully helpful.

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 clear parameter descriptions and an enum for priority values. The description adds no additional meaning beyond the schema, such as explaining priority semantics or issueId formats. Baseline 3 is appropriate since the schema adequately documents parameters.

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 'Set the priority of an issue' clearly states the action (set) and target (priority of an issue), but it's vague about scope and lacks differentiation from siblings like linear_updateIssue, which might also handle priority updates. It doesn't specify if this is a dedicated tool or part of a broader update operation.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention whether to prefer linear_setIssuePriority over linear_updateIssue for priority changes, or if there are prerequisites like issue accessibility. The description offers no context for tool selection among siblings.

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