Skip to main content
Glama
tiovikram

Linear MCP Server

by tiovikram

list_issues

Retrieve Linear issues with filters for team, assignee, or status to manage project tasks effectively.

Instructions

List issues with optional filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdNoFilter by team ID (optional)
assigneeIdNoFilter by assignee ID (optional)
statusNoFilter by status (optional)
firstNoNumber of issues to return (default: 50)

Implementation Reference

  • The main handler function for the 'list_issues' tool. It parses input arguments, constructs a filter for team, assignee, and status, queries the Linear API for issues, formats the results with additional details like status and assignee names, and returns the data as a JSON string in the MCP response format.
    case "list_issues": {
      const args = request.params.arguments as unknown as ListIssuesArgs;
      const filter: Record<string, any> = {};
      if (args?.teamId) filter.team = { id: { eq: args.teamId } };
      if (args?.assigneeId) filter.assignee = { id: { eq: args.assigneeId } };
      if (args?.status) filter.state = { name: { eq: args.status } };
    
      const issues = await linearClient.issues({
        first: args?.first ?? 50,
        filter,
      });
    
      const formattedIssues = await Promise.all(
        issues.nodes.map(async (issue) => {
          const state = await issue.state;
          const assignee = await issue.assignee;
          return {
            id: issue.id,
            title: issue.title,
            status: state ? await state.name : "Unknown",
            assignee: assignee ? assignee.name : "Unassigned",
            priority: issue.priority,
            url: issue.url,
          };
        })
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(formattedIssues, null, 2),
          },
        ],
      };
    }
  • JSON schema defining the input parameters for the 'list_issues' tool, used for validation in MCP tool calls.
    inputSchema: {
      type: "object",
      properties: {
        teamId: {
          type: "string",
          description: "Filter by team ID (optional)",
        },
        assigneeId: {
          type: "string",
          description: "Filter by assignee ID (optional)",
        },
        status: {
          type: "string",
          description: "Filter by status (optional)",
        },
        first: {
          type: "number",
          description: "Number of issues to return (default: 50)",
        },
      },
    },
  • src/index.ts:100-124 (registration)
    Registration of the 'list_issues' tool in the ListToolsRequestSchema handler, specifying name, description, and input schema.
    {
      name: "list_issues",
      description: "List issues with optional filters",
      inputSchema: {
        type: "object",
        properties: {
          teamId: {
            type: "string",
            description: "Filter by team ID (optional)",
          },
          assigneeId: {
            type: "string",
            description: "Filter by assignee ID (optional)",
          },
          status: {
            type: "string",
            description: "Filter by status (optional)",
          },
          first: {
            type: "number",
            description: "Number of issues to return (default: 50)",
          },
        },
      },
    },
  • src/index.ts:46-54 (registration)
    Capabilities declaration indicating support for the 'list_issues' tool among others.
    tools: {
      create_issue: true,
      list_issues: true,
      update_issue: true,
      list_teams: true,
      list_projects: true,
      search_issues: true,
      get_issue: true,
    },
  • TypeScript type definition for 'ListIssuesArgs' used for type casting input arguments in the handler.
    type ListIssuesArgs = {
      teamId?: string;
      assigneeId?: string;
      status?: string;
      first?: 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 only mentions 'optional filters', failing to describe key traits such as pagination behavior (implied by 'first' parameter), rate limits, authentication needs, or whether it's read-only. This is a significant gap for a tool with multiple parameters and no output schema.

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 with zero waste. It's appropriately sized and front-loaded, making it easy to parse quickly 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?

Given the tool's complexity (4 parameters, no annotations, no output schema, and multiple sibling tools), the description is incomplete. It lacks details on behavioral traits, usage differentiation, and output expectations, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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 fully documents all four parameters. The description adds no meaning beyond the schema, merely restating that filters are optional without explaining parameter interactions or semantics. Baseline 3 is appropriate as 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 'List issues with optional filters' states the basic action (list) and resource (issues), but it's vague about scope and doesn't differentiate from sibling tools like 'search_issues' or 'get_issue'. It lacks specificity about what 'list' entails (e.g., all issues, paginated, sorted).

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 like 'search_issues' or 'get_issue'. The description mentions 'optional filters' but doesn't specify contexts or exclusions, leaving the agent to infer usage from the tool name 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/tiovikram/linear-mcp'

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