Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_getProjectIssues

Retrieve all issues from a specific Linear project to track progress, manage tasks, and monitor project status.

Instructions

Get all issues associated with a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesID of the project to get issues for
limitNoMaximum number of issues to return (default: 25)

Implementation Reference

  • Handler function that executes the tool logic: validates input args using isGetProjectIssuesArgs and calls linearService.getProjectIssues(projectId, limit).
    export function handleGetProjectIssues(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isGetProjectIssuesArgs(args)) {
            throw new Error("Invalid arguments for getProjectIssues");
          }
          
          return await linearService.getProjectIssues(args.projectId, args.limit);
        } catch (error) {
          logError("Error getting project issues", error);
          throw error;
        }
      };
    } 
  • MCP tool definition with input/output schemas for linear_getProjectIssues.
    export const getProjectIssuesToolDefinition: MCPToolDefinition = {
      name: "linear_getProjectIssues",
      description: "Get all issues associated with a project",
      input_schema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "ID of the project to get issues for",
          },
          limit: {
            type: "number",
            description: "Maximum number of issues to return (default: 25)",
          },
        },
        required: ["projectId"],
      },
      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" },
            team: { type: "object" },
            assignee: { type: "object" },
            url: { type: "string" }
          }
        }
      }
    }; 
  • Registration of the linear_getProjectIssues tool handler in the registerToolHandlers function.
    linear_getProjectIssues: handleGetProjectIssues(linearService),
  • Type guard function for validating the input arguments of the linear_getProjectIssues tool.
    export function isGetProjectIssuesArgs(args: unknown): args is {
      projectId: string;
      limit?: number;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "projectId" in args &&
        typeof (args as { projectId: string }).projectId === "string" &&
        (!("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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Get all issues') but doesn't describe key behaviors like pagination (implied by 'limit' parameter), error handling, authentication needs, rate limits, or what 'all issues' entails (e.g., status filters). This is a significant gap for a read operation with no annotation coverage.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with no wasted information.

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 retrieving issues (which may involve filtering, pagination, or permissions) and the lack of annotations and output schema, the description is incomplete. It doesn't address return values, error cases, or behavioral nuances, making it inadequate for a tool with two parameters and no structured output documentation.

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 clear descriptions for 'projectId' and 'limit' parameters. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain format constraints for 'projectId' or how 'limit' interacts with pagination), so it meets the baseline for high schema coverage.

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 verb ('Get') and resource ('issues associated with a project'), making the purpose understandable. However, it doesn't distinguish this from sibling tools like 'linear_getIssues' or 'linear_searchIssues', which also retrieve issues, so it lacks sibling differentiation.

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. It doesn't mention when to prefer this over 'linear_getIssues' (which might retrieve issues without project filtering) or 'linear_searchIssues' (which might offer more flexible querying), leaving the agent without usage context.

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