Skip to main content
Glama

linear_subscribeToIssue

Subscribe to receive notifications for updates on a specific Linear issue. Stay informed when changes occur to tasks or bugs in your project management workflow.

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

  • The primary handler implementation for the 'linear_subscribeToIssue' tool. Validates input arguments and calls the Linear service method to subscribe 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;
        }
      };
    }
  • The tool schema definition for 'linear_subscribeToIssue', specifying input (issueId) and output schemas.
    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 tool handler in the map returned by registerToolHandlers, mapping 'linear_subscribeToIssue' to the handleSubscribeToIssue factory.
    linear_subscribeToIssue: handleSubscribeToIssue(linearService),
  • Type guard function used in the handler to validate arguments for 'linear_subscribeToIssue' tool.
    /**
     * 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?

With no annotations provided, the description carries full burden but reveals minimal behavior. 'Subscribe' implies a persistent action, but it doesn't disclose whether this creates email/webhook notifications, requires specific permissions, has rate limits, or what confirmation/response to expect. 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 maximally concise at just four words. Every word earns its place by specifying the action ('subscribe'), target ('issue'), and scope ('updates'). There's no wasted language or unnecessary elaboration for this straightforward operation.

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 incomplete. It doesn't explain what 'subscribe' means operationally, what permissions are needed, what the expected outcome is, or how to verify subscription status. The agent lacks sufficient context to use this tool effectively.

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 the single parameter 'issueId' well-documented in the schema. The description adds no additional parameter context beyond what's already in the schema, so it meets the baseline for high schema coverage but doesn't enhance understanding of the parameter's role in subscription.

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 vague about what 'subscribe' entails - whether it's email notifications, webhook subscriptions, or in-app alerts. It doesn't distinguish from siblings like linear_getIssueHistory or linear_updateIssue which also relate to issue tracking.

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 about when to use this tool versus alternatives. There's no mention of prerequisites (like needing issue access), when subscription is appropriate versus just checking issue history, or what happens if already subscribed. The description offers no context for tool selection.

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