Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_subscribeToIssue

Subscribe to receive notifications about updates for a specific Linear issue by providing its ID, enabling you to stay informed on changes.

Instructions

Subscribe to issue updates

Input Schema

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

Implementation Reference

  • Handler function that validates arguments using isSubscribeToIssueArgs and calls linearService.subscribeToIssue to subscribe the current user to the specified issue.
    export function handleSubscribeToIssue(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isSubscribeToIssueArgs(args)) {
            throw new Error("Invalid arguments for subscribeToIssue");
          }
          
          return await linearService.subscribeToIssue(args.issueId);
        } catch (error) {
          logError("Error subscribing to issue", error);
          throw error;
        }
      };
    }
  • MCP tool definition including name, description, input schema (requires issueId), and output schema (success boolean and message).
    export const subscribeToIssueToolDefinition: MCPToolDefinition = {
      name: "linear_subscribeToIssue",
      description: "Subscribe to issue updates",
      input_schema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "ID or identifier of the issue to subscribe to (e.g., ABC-123)",
          },
        },
        required: ["issueId"],
      },
      output_schema: {
        type: "object",
        properties: {
          success: { type: "boolean" },
          message: { type: "string" }
        }
      }
    };
  • Registration of the linear_subscribeToIssue handler within the registerToolHandlers function, mapping the tool name to handleSubscribeToIssue curried with LinearService.
    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 to validate input arguments for the linear_subscribeToIssue tool, ensuring issueId is a string.
     * Type guard for linear_subscribeToIssue tool arguments
     */
    export function isSubscribeToIssueArgs(args: unknown): args is {
      issueId: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "issueId" in args &&
        typeof (args as { issueId: string }).issueId === "string"
      );
    }
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. It mentions 'subscribe to issue updates' but doesn't disclose behavioral traits such as whether this requires authentication, what type of updates are subscribed to (e.g., comments, status changes), if it's idempotent, or how subscriptions are managed (e.g., duration, cancellation). The description is minimal and lacks critical operational details.

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 extremely concise with a single phrase 'Subscribe to issue updates', which is front-loaded and wastes no words. Every word earns its place by directly conveying the tool's purpose without redundancy or fluff.

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 complexity of a subscription tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'subscribe' means in practice, what the tool returns (e.g., confirmation, subscription ID), or any side effects (e.g., notifications setup). For a tool that likely involves ongoing updates, more context is needed to be fully helpful.

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 has 100% description coverage, with the 'issueId' parameter well-documented as 'ID or identifier of the issue to subscribe to (e.g., ABC-123)'. The description adds no additional meaning beyond this, as it doesn't elaborate on parameter usage or constraints. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Subscribe to issue updates' clearly states the action (subscribe) and target (issue updates), but it's somewhat vague about what 'subscribe' entails (e.g., notifications, webhooks, email alerts). It distinguishes from siblings by focusing on subscription rather than creation, assignment, or modification, but lacks specificity about the subscription mechanism.

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. It doesn't mention prerequisites (e.g., needing an existing issue), exclusions (e.g., not for unauthenticated users), or related tools (e.g., how it differs from linear_getIssueById for monitoring changes). The context is implied but not explicitly stated.

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