Skip to main content
Glama

linear_assignIssue

Assign a Linear issue to a specific team member or unassign it to manage task ownership and workflow distribution.

Instructions

Assign an issue to a user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesID or identifier of the issue to assign (e.g., ABC-123)
assigneeIdYesID of the user to assign the issue to, or null to unassign

Implementation Reference

  • The main handler function for the linear_assignIssue tool. It validates arguments using isAssignIssueArgs and calls linearService.assignIssue to perform the assignment.
    /**
     * Handler for assigning an issue to a user
     */
    export function handleAssignIssue(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isAssignIssueArgs(args)) {
            throw new Error('Invalid arguments for assignIssue');
          }
    
          return await linearService.assignIssue(args.issueId, args.assigneeId);
        } catch (error) {
          logError('Error assigning issue', error);
          throw error;
        }
      };
    }
  • The tool definition including input_schema and output_schema for linear_assignIssue.
    export const assignIssueToolDefinition: MCPToolDefinition = {
      name: 'linear_assignIssue',
      description: 'Assign an issue to a user',
      input_schema: {
        type: 'object',
        properties: {
          issueId: {
            type: 'string',
            description: 'ID or identifier of the issue to assign (e.g., ABC-123)',
          },
          assigneeId: {
            type: 'string',
            description: 'ID of the user to assign the issue to, or null to unassign',
          },
        },
        required: ['issueId', 'assigneeId'],
      },
      output_schema: {
        type: 'object',
        properties: {
          success: { type: 'boolean' },
          issue: {
            type: 'object',
            properties: {
              id: { type: 'string' },
              identifier: { type: 'string' },
              title: { type: 'string' },
              assignee: { type: 'object' },
              url: { type: 'string' },
            },
          },
        },
      },
    };
  • Registration of the linear_assignIssue tool mapping to the handleAssignIssue handler function.
    linear_assignIssue: handleAssignIssue(linearService),
  • Type guard function used in the handler to validate arguments for linear_assignIssue.
     * Type guard for linear_assignIssue tool arguments
     */
    export function isAssignIssueArgs(args: unknown): args is {
      issueId: string;
      assigneeId: string;
    } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'issueId' in args &&
        typeof (args as { issueId: string }).issueId === 'string' &&
        'assigneeId' in args &&
        typeof (args as { assigneeId: string }).assigneeId === 'string'
      );
    }
  • Import of the handleAssignIssue function from issue-handlers.ts for use in tool registration.
    import {
      handleGetIssues,
      handleGetIssueById,
      handleSearchIssues,
      handleCreateIssue,
      handleUpdateIssue,
      handleCreateComment,
      handleAddIssueLabel,
      handleRemoveIssueLabel,
      // New Issue Management handlers
      handleAssignIssue,
      handleSubscribeToIssue,
      handleConvertIssueToSubtask,
      handleCreateIssueRelation,
      handleArchiveIssue,
      handleSetIssuePriority,
      handleTransferIssue,
      handleDuplicateIssue,
      handleGetIssueHistory,
      // Comment Management handlers
      handleGetComments,
    } from './issue-handlers.js';
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. While 'Assign' implies a mutation operation, the description doesn't mention permissions required, whether this action is reversible, what happens to previous assignees, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral transparency.

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 extremely concise at just 5 words, front-loading the core purpose without any wasted words. Every word earns its place, making it easy to parse and understand quickly.

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 inadequate. It doesn't explain what happens after assignment, whether there are side effects, what permissions are required, or what the tool returns. Given the complexity of assignment operations and the lack of structured documentation, the description should provide more 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?

The schema description coverage is 100%, with both parameters clearly documented in the input schema. The description doesn't add any meaningful parameter information beyond what's already in the structured schema, so it meets the baseline expectation but doesn't provide additional value.

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 ('Assign') and resource ('an issue to a user'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like linear_updateIssue (which might also handle assignments) or linear_transferIssue, so it doesn't fully distinguish from alternatives.

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 sibling tools like linear_updateIssue and linear_transferIssue that might handle similar functionality, there's no indication of when this specific assignment tool is preferred or when other approaches should be used instead.

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