Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_getIssues

Retrieve recent issues from Linear's project management system to track tasks and monitor progress. Specify a limit to control the number of issues returned.

Instructions

Get a list of recent issues from Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of issues to return (default: 10)

Implementation Reference

  • The main handler function for the 'linear_getIssues' tool. It validates the input arguments using the type guard and delegates to LinearService.getIssues(limit).
    export function handleGetIssues(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isGetIssuesArgs(args)) {
            throw new Error("Invalid arguments for getIssues");
          }
          
          return await linearService.getIssues(args.limit);
        } catch (error) {
          logError("Error getting issues", error);
          throw error;
        }
      };
    }
  • The MCPToolDefinition for 'linear_getIssues', including input and output schemas.
    export const getIssuesToolDefinition: MCPToolDefinition = {
      name: "linear_getIssues",
      description: "Get a list of recent issues from Linear",
      input_schema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Maximum number of issues to return (default: 10)",
          },
        }
      },
      output_schema: {
        type: "array",
        items: {
          type: "object",
          properties: {
            id: { type: "string" },
            identifier: { type: "string" },
            title: { type: "string" },
            description: { type: "string" },
            state: { type: "string" },
            priority: { type: "number" },
            estimate: { type: "number" },
            dueDate: { type: "string" },
            team: { type: "object" },
            assignee: { type: "object" },
            project: { type: "object" },
            cycle: { type: "object" },
            parent: { type: "object" },
            labels: { 
              type: "array",
              items: {
                type: "object",
                properties: {
                  id: { type: "string" },
                  name: { type: "string" },
                  color: { type: "string" }
                }
              }
            },
            sortOrder: { type: "number" },
            createdAt: { type: "string" },
            updatedAt: { type: "string" },
            url: { type: "string" }
          }
        }
      }
    };
  • The registration of the 'linear_getIssues' handler within the registerToolHandlers function, which maps tool names to their handler functions.
    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 used in the handler to validate input arguments for 'linear_getIssues'.
    export function isGetIssuesArgs(args: unknown): args is { limit?: number } {
      return (
        typeof args === "object" &&
        args !== null &&
        (!("limit" in args) || typeof (args as { limit: number }).limit === "number")
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves a list but lacks details on permissions, rate limits, pagination, or what 'recent' entails (e.g., time-based or count-based). This is inadequate for a tool that likely interacts with an external API and has behavioral nuances.

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 that front-loads the core purpose without unnecessary words. It's appropriately sized for a simple tool, though it could benefit from additional context without sacrificing conciseness.

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 fetching issues from Linear (likely involving API constraints) and the lack of annotations and output schema, the description is incomplete. It doesn't cover return format, error handling, or how 'recent' is determined, leaving gaps that could hinder effective tool use by an agent.

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 fully documents the single parameter 'limit'. The description adds no additional parameter semantics beyond implying 'recent' issues, which isn't tied to any documented parameter. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Get a list') and resource ('recent issues from Linear'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'linear_searchIssues' or 'linear_getIssueById', which would require more specificity about scope or filtering capabilities.

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 like 'linear_searchIssues' or 'linear_getProjectIssues'. It mentions 'recent issues' but doesn't clarify what 'recent' means or whether this is for unfiltered listing versus targeted queries, leaving the agent with insufficient 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/wkoutre/linear-mcp-server'

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