Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_assignIssue

Assign Linear issues to specific team members or unassign them 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 core handler function that executes the linear_assignIssue tool. Validates input with isAssignIssueArgs type guard and delegates to LinearService.assignIssue.
    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 MCP tool definition (schema) for linear_assignIssue, including input and output schemas.
    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 handler in the tool handlers registry.
    linear_assignIssue: handleAssignIssue(linearService),
  • Type guard function used in the handler to validate arguments for linear_assignIssue.
    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"
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Assign an issue to a user' implies a mutation operation but doesn't specify permissions required, whether this action is reversible, what happens to previous assignees, or error conditions. For a mutation tool with zero annotation coverage, this is insufficient.

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 wasted words. It's perfectly front-loaded and efficiently communicates the core purpose without unnecessary elaboration.

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 when assignment succeeds or fails, doesn't mention permissions or side effects, and provides no context about the Linear system's assignment behavior. The description should do more given the complexity of the operation.

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%, so the input schema already fully documents both parameters (issueId and assigneeId). The description adds no additional parameter information beyond what's in the schema, which is acceptable given the comprehensive schema coverage.

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 likely also handles assignments) or linear_transferIssue, so it doesn't reach the highest score.

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 siblings 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 tools 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/wkoutre/linear-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server