Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_searchIssues

Find and filter project issues by text, team, assignee, project, or status to manage tasks effectively in Linear.

Instructions

Search for issues with various filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoText to search for in issue title or description
teamIdNoFilter issues by team ID
assigneeIdNoFilter issues by assignee ID
projectIdNoFilter issues by project ID
statesNoFilter issues by state name (e.g., 'Todo', 'In Progress', 'Done')
limitNoMaximum number of issues to return (default: 10)

Implementation Reference

  • The handler function that implements the core logic for the 'linear_searchIssues' tool. It performs argument validation using the type guard and calls the Linear service's searchIssues method.
    export function handleSearchIssues(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          console.log("searchIssues args:", JSON.stringify(args, null, 2));
          
          if (!isSearchIssuesArgs(args)) {
            console.error("Invalid arguments for searchIssues");
            throw new Error("Invalid arguments for searchIssues");
          }
          
          console.log("Arguments validated successfully");
          return await linearService.searchIssues(args);
        } catch (error) {
          logError("Error searching issues", error);
          throw error;
        }
      };
    }
  • The tool schema definition for 'linear_searchIssues', specifying input parameters (query, filters, limit) and output format (array of issue objects).
    export const searchIssuesToolDefinition: MCPToolDefinition = {
      name: "linear_searchIssues",
      description: "Search for issues with various filters",
      input_schema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Text to search for in issue title or description",
          },
          teamId: {
            type: "string",
            description: "Filter issues by team ID",
          },
          assigneeId: {
            type: "string",
            description: "Filter issues by assignee ID",
          },
          projectId: {
            type: "string",
            description: "Filter issues by project ID",
          },
          states: {
            type: "array",
            items: { type: "string" },
            description: "Filter issues by state name (e.g., 'Todo', 'In Progress', 'Done')",
          },
          limit: {
            type: "number",
            description: "Maximum number of issues to return (default: 10)",
          },
        },
        required: [],
      },
      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" }
          }
        }
      }
    };
  • Registration of the 'linear_searchIssues' handler within the registerToolHandlers function, mapping the tool name to the handler factory.
    linear_searchIssues: handleSearchIssues(linearService),
  • Type guard function used by the handler to validate input arguments for 'linear_searchIssues'.
    export function isSearchIssuesArgs(args: unknown): args is {
      query?: string;
      teamId?: string;
      assigneeId?: string;
      projectId?: string;
      states?: string[];
      limit?: number;
    } {
      // Check if args is an object
      if (typeof args !== "object" || args === null) {
        console.error("searchIssues args is not an object or is null");
        return false;
      }
    
      // Check query
      if ("query" in args && typeof (args as { query: unknown }).query !== "string") {
        console.error("searchIssues query is not a string");
        return false;
      }
    
      // Check teamId
      if ("teamId" in args && typeof (args as { teamId: unknown }).teamId !== "string") {
        console.error("searchIssues teamId is not a string");
        return false;
      }
    
      // Check assigneeId
      if ("assigneeId" in args && typeof (args as { assigneeId: unknown }).assigneeId !== "string") {
        console.error("searchIssues assigneeId is not a string");
        return false;
      }
    
      // Check projectId
      if ("projectId" in args && typeof (args as { projectId: unknown }).projectId !== "string") {
        console.error("searchIssues projectId is not a string");
        return false;
      }
    
      // Check states
      if ("states" in args) {
        const states = (args as { states: unknown }).states;
        if (!Array.isArray(states)) {
          console.error("searchIssues states is not an array");
          return false;
        }
        
        // Check that all elements in the array are strings
        for (let i = 0; i < states.length; i++) {
          if (typeof states[i] !== "string") {
            console.error(`searchIssues states[${i}] is not a string`);
            return false;
          }
        }
      }
    
      // Check limit
      if ("limit" in args && typeof (args as { limit: unknown }).limit !== "number") {
        console.error("searchIssues limit is not a number");
        return false;
      }
    
      return true;
    }
  • Inclusion of the searchIssuesToolDefinition in the allToolDefinitions array for overall tool registration.
    getIssuesToolDefinition,
    getIssueByIdToolDefinition,
    searchIssuesToolDefinition,
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. It mentions 'various filters' but doesn't specify search behavior (e.g., full-text vs. exact match, pagination, rate limits, authentication needs, or what happens with no results). For a search tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's appropriately sized for a search tool, though it could be more front-loaded with critical details like distinguishing from siblings or behavioral traits.

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 search tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on return values, error handling, performance constraints, and differentiation from sibling tools, making it inadequate for informed tool selection.

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 schema already documents all 6 parameters thoroughly. The description adds no additional meaning beyond implying filter usage, which is redundant with the schema. Baseline 3 is appropriate when the schema does the heavy lifting, but no extra value is added.

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 'Search for issues with various filters' states the verb (search) and resource (issues), but it's vague about scope and specificity. It doesn't distinguish this from sibling tools like 'linear_getIssues' or 'linear_getProjectIssues', leaving ambiguity about when to use this versus other issue retrieval tools.

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. With multiple sibling tools for retrieving issues (e.g., linear_getIssues, linear_getProjectIssues), the description offers no context about prerequisites, typical use cases, or exclusions, leaving the agent to guess based on tool names alone.

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