Skip to main content
Glama

linear_transferIssue

Transfer an issue to another team in Linear project management. Specify the issue ID and target team ID to move tasks between teams.

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 implements the core logic for the 'linear_transferIssue' tool. It validates the input arguments using a type guard and calls the LinearService to perform the issue transfer.
    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;
        }
      };
    }
  • The tool definition including input and output schemas for 'linear_transferIssue'.
    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' },
            },
          },
        },
      },
    };
  • Registration of the handler for 'linear_transferIssue' in the tool handlers registry.
    linear_transferIssue: handleTransferIssue(linearService),
  • Type guard function for validating arguments to the 'linear_transferIssue' tool.
    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'
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without behavioral details. It doesn't disclose whether this requires specific permissions, if it's reversible, what happens to existing assignments or labels, or any side effects like notifications. For a mutation tool with zero annotation coverage, this is a significant gap in 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 a single, efficient sentence with zero waste—it directly states the tool's purpose without redundancy or fluff. It's appropriately sized and front-loaded, making it easy to parse 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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, reversibility), output expectations, or error conditions. While the schema covers parameters well, the overall context for safe and effective use is insufficient.

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 and teamId) clearly documented in the schema. The description adds no additional meaning beyond implying these parameters are used for transfer, which the schema already covers. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('an issue'), specifying the destination ('to another team'). It distinguishes from siblings like linear_assignIssue (assigns to user) or linear_updateIssue (general updates), though not explicitly. However, it lacks specific differentiation details like whether this changes ownership or just team association.

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 prerequisites (e.g., issue must be unassigned or in a specific state), exclusions (e.g., cannot transfer archived issues), or comparisons to siblings like linear_updateIssue (which might allow team changes as part of broader updates). The description implies usage for team transfers but offers no contextual rules.

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