Skip to main content
Glama
Sign In
Linear

Linear

by tacticlaunch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

linear_transferIssue

Idempotent

Transfer an issue to another team in Linear by providing the issue ID and target team ID.

Instructions

Transfer an issue to another team

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issueId": "<issueId>",
      "teamId": "<teamId>"
    },
    "name": "linear_transferIssue"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
issueNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.2
    • changedOutput schema / properties / issue / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed1 schema field changedv1.4.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "issue": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "identifier": {
+          "type": "string"
+        },
+        "team": {
+          "type": "object"
+        },
+        "title": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false (mutation), destructiveHint=false, and idempotentHint=true. The description adds no behavioral detail beyond the bare action, such as whether the transfer affects issue history, other fields, or requires the target team to exist. It does not contradict annotations, but with the burden shifted to the description, it fails to disclose any side effects or prerequisites.

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 zero fluff. It is front-loaded with the core action and avoids unnecessary detail. This is exemplary conciseness for a straightforward tool.

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

Completeness3/5

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

Given the moderate complexity of transferring an issue and the existence of an output schema, the description is minimally sufficient but lacks contextual details about side effects or preconditions. An agent can call the tool, but might be unaware of implications like changes to the issue's project or cycle. The description does not explicitly mention any constraints or consequences, leaving some gaps for a complete understanding.

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 input schema provides clear, complete descriptions for both parameters (teamId and issueId) with 100% coverage. The description does not add any additional parameter semantics—it only restates the action. Baseline 3 is appropriate because the schema already carries the parameter information and the description does not enhance it.

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 'Transfer an issue to another team' clearly states the action (transfer) and the resource (issue) plus the destination (another team). It is specific and easily distinguishable from siblings like linear_updateIssue or linear_assignIssue, which deal with different modifications. The verb and noun combination makes the purpose unambiguous.

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. It does not mention conditions (e.g., requiring specific permissions, whether the issue must be open, or differences from assignIssue or updateIssue). An agent must infer usage solely from the name and general context, offering insufficient decision support.

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

Deploy Server

Other Tools