Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_transferIssue

Transfer issues between teams in Linear to reorganize work and align responsibilities.

Instructions

Transfer an issue to another team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesID or identifier of the issue to transfer (e.g., ABC-123)
teamIdYesID of the team to transfer the issue to

Implementation Reference

  • The handler function that executes the linear_transferIssue tool logic, including argument validation and calling the Linear service to transfer the issue to a new team.
    /**
     * Handler for transferring an issue
     */
    export function handleTransferIssue(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isTransferIssueArgs(args)) {
            throw new Error("Invalid arguments for transferIssue");
          }
          
          return await linearService.transferIssue(args.issueId, args.teamId);
        } catch (error) {
          logError("Error transferring issue", error);
          throw error;
        }
      };
    }
  • Defines the input schema (issueId, teamId) and output schema for the linear_transferIssue tool.
    export const transferIssueToolDefinition: MCPToolDefinition = {
      name: "linear_transferIssue",
      description: "Transfer an issue to another team",
      input_schema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "ID or identifier of the issue to transfer (e.g., ABC-123)",
          },
          teamId: {
            type: "string",
            description: "ID of the team to transfer the issue to",
          },
        },
        required: ["issueId", "teamId"],
      },
      output_schema: {
        type: "object",
        properties: {
          success: { type: "boolean" },
          issue: {
            type: "object",
            properties: {
              id: { type: "string" },
              identifier: { type: "string" },
              title: { type: "string" },
              team: { type: "object" },
              url: { type: "string" }
            }
          }
        }
      }
    };
  • Registers the linear_transferIssue tool by mapping the name to the handleTransferIssue handler function within the tool handlers registry.
    export function registerToolHandlers(linearService: LinearService) {
      return {
        // User tools
        linear_getViewer: handleGetViewer(linearService),
        linear_getOrganization: handleGetOrganization(linearService),
        linear_getUsers: handleGetUsers(linearService),
        linear_getLabels: handleGetLabels(linearService),
    
        // Team tools
        linear_getTeams: handleGetTeams(linearService),
        linear_getWorkflowStates: handleGetWorkflowStates(linearService),
    
        // Project tools
        linear_getProjects: handleGetProjects(linearService),
        linear_createProject: handleCreateProject(linearService),
        
        // Project Management tools
        linear_updateProject: handleUpdateProject(linearService),
        linear_addIssueToProject: handleAddIssueToProject(linearService),
        linear_getProjectIssues: handleGetProjectIssues(linearService),
        
        // Cycle Management tools
        linear_getCycles: handleGetCycles(linearService),
        linear_getActiveCycle: handleGetActiveCycle(linearService),
        linear_addIssueToCycle: handleAddIssueToCycle(linearService),
    
        // Issue tools
        linear_getIssues: handleGetIssues(linearService),
        linear_getIssueById: handleGetIssueById(linearService),
        linear_searchIssues: handleSearchIssues(linearService),
        linear_createIssue: handleCreateIssue(linearService),
        linear_updateIssue: handleUpdateIssue(linearService),
        linear_createComment: handleCreateComment(linearService),
        linear_addIssueLabel: handleAddIssueLabel(linearService),
        linear_removeIssueLabel: handleRemoveIssueLabel(linearService),
        
        // New Issue Management tools
        linear_assignIssue: handleAssignIssue(linearService),
        linear_subscribeToIssue: handleSubscribeToIssue(linearService),
        linear_convertIssueToSubtask: handleConvertIssueToSubtask(linearService),
        linear_createIssueRelation: handleCreateIssueRelation(linearService),
        linear_archiveIssue: handleArchiveIssue(linearService),
        linear_setIssuePriority: handleSetIssuePriority(linearService),
        linear_transferIssue: handleTransferIssue(linearService),
        linear_duplicateIssue: handleDuplicateIssue(linearService),
        linear_getIssueHistory: handleGetIssueHistory(linearService),
        
        // Comment Management tools
        linear_getComments: handleGetComments(linearService)
      };
    }
  • Type guard function used to validate the input arguments for the linear_transferIssue tool.
    /**
     * Type guard for linear_transferIssue tool arguments
     */
    export function isTransferIssueArgs(args: unknown): args is {
      issueId: string;
      teamId: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "issueId" in args &&
        typeof (args as { issueId: string }).issueId === "string" &&
        "teamId" in args &&
        typeof (args as { teamId: string }).teamId === "string"
      );
    }
  • Includes the transferIssueToolDefinition in the array of all tool definitions for registration.
    export const allToolDefinitions: MCPToolDefinition[] = [
      // User tools
      getViewerToolDefinition,
      getOrganizationToolDefinition,
      getUsersToolDefinition,
      getLabelsToolDefinition,
      
      // Team tools
      getTeamsToolDefinition,
      getWorkflowStatesToolDefinition,
      
      // Project tools
      getProjectsToolDefinition,
      createProjectToolDefinition,
      
      // Project Management tools
      updateProjectToolDefinition,
      addIssueToProjectToolDefinition,
      getProjectIssuesToolDefinition,
      
      // Cycle Management tools
      getCyclesToolDefinition,
      getActiveCycleToolDefinition,
      addIssueToCycleToolDefinition,
      
      // Issue tools
      getIssuesToolDefinition,
      getIssueByIdToolDefinition,
      searchIssuesToolDefinition,
      createIssueToolDefinition,
      updateIssueToolDefinition,
      createCommentToolDefinition,
      addIssueLabelToolDefinition,
      removeIssueLabelToolDefinition,
      
      // New Issue Management tools
      assignIssueToolDefinition,
      subscribeToIssueToolDefinition,
      convertIssueToSubtaskToolDefinition,
      createIssueRelationToolDefinition,
      archiveIssueToolDefinition,
      setIssuePriorityToolDefinition,
      transferIssueToolDefinition,
      duplicateIssueToolDefinition,
      getIssueHistoryToolDefinition,
      
      // Comment Management tools
      getCommentsToolDefinition
    ];

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits. It only names the action 'transfer' without detailing effects on existing assignments, comments, or permissions. The agent is left without critical context about side effects.

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, clear sentence with no fluff. It efficiently communicates the tool's purpose without unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 required params, no output schema), the description combined with the schema is nearly sufficient. However, a note about retaining issue data (e.g., comments, labels) would make it fully complete.

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 coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond the schema, but it does not contradict it. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action (transfer) and the resource (issue) along with the destination (another team). It directly communicates the tool's function and distinguishes it from sibling tools like linear_assignIssue or linear_updateIssue.

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, such as when to transfer vs. assign or update an issue. No context about prerequisites or exclusions is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.