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
    ];
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Transfer' suggests a mutation operation, but the description doesn't specify if this is reversible, requires permissions, affects issue history, or has side effects (e.g., notifications). It misses key behavioral traits like whether the transfer preserves issue data or resets fields, making it inadequate for a mutation tool with zero annotation coverage.

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 with zero waste—'Transfer an issue to another team'—front-loading the core action. It's appropriately sized for a simple tool, avoiding unnecessary elaboration while clearly stating the purpose. Every word earns its place, 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 mutation nature (transfer implies write operation), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions, reversibility, or response format, which are critical for an agent to use it correctly. For a 2-param mutation tool with no structured support, more context is needed to be adequately 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 description coverage is 100%, with both parameters (issueId, teamId) documented in the schema. The description adds no additional meaning beyond implying these parameters are used for transfer, but it doesn't clarify format (e.g., teamId source) or constraints. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't detract either.

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 ('transfer') and resource ('issue'), specifying the target ('to another team'). It distinguishes this from sibling tools like linear_assignIssue (assigns to user) or linear_updateIssue (general updates), though it doesn't explicitly name alternatives. The purpose is specific but could be more precise about what 'transfer' entails (e.g., moving ownership vs. copying).

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 like linear_assignIssue or linear_updateIssue, nor does it mention prerequisites (e.g., needing issue and team IDs). It implies usage for moving issues between teams but lacks context on exclusions (e.g., if the issue is archived) or best practices, leaving the agent to infer from tool names alone.

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