Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_getProjects

Retrieve a list of projects from Linear's project management system to view, organize, and manage team workflows and tasks.

Instructions

Get a list of projects from Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'linear_getProjects' tool. It takes no input arguments (as per schema), calls LinearService.getProjects(), and handles errors by logging and rethrowing.
    export function handleGetProjects(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getProjects();
        } catch (error) {
          logError("Error getting projects", error);
          throw error;
        }
      };
    }
  • Tool schema definition specifying empty input and detailed output structure for projects including id, name, description, state, teams array, and url.
    export const getProjectsToolDefinition: MCPToolDefinition = {
      name: "linear_getProjects",
      description: "Get a list of projects from Linear",
      input_schema: {
        type: "object",
        properties: {},
      },
      output_schema: {
        type: "array",
        items: {
          type: "object",
          properties: {
            id: { type: "string" },
            name: { type: "string" },
            description: { type: "string" },
            state: { type: "string" },
            teams: {
              type: "array",
              items: {
                type: "object",
                properties: {
                  id: { type: "string" },
                  name: { type: "string" }
                }
              }
            },
            url: { type: "string" }
          }
        }
      }
    };
  • Tool registration mapping the name 'linear_getProjects' to its handler function within the registerToolHandlers export.
    linear_getProjects: handleGetProjects(linearService),
  • Core service method implementing the project fetching logic using Linear client SDK, resolving projects and their teams asynchronously. Called by the tool handler.
    async getProjects() {
      const projects = await this.client.projects();
      return Promise.all(
        projects.nodes.map(async (project) => {
          // We need to fetch teams using the relationship
          const teams = await project.teams();
    
          return {
            id: project.id,
            name: project.name,
            description: project.description,
            state: project.state,
            teams: teams.nodes.map((team) => ({
              id: team.id,
              name: team.name,
            })),
          };
        }),
      );
    }
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 this is a read operation ('Get'), but doesn't mention any behavioral traits such as authentication requirements, rate limits, pagination, sorting, or what data is included in the list. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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, clear sentence with no wasted words. It's front-loaded with the core purpose ('Get a list of projects from Linear'), making it highly efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema) and lack of annotations, the description is minimally adequate but incomplete. It states what the tool does but doesn't cover behavioral aspects like response format, error handling, or usage context relative to siblings. For a basic read tool, it meets the minimum but leaves room for improvement in guiding effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% description coverage, so no parameters need documentation. The description doesn't add parameter information, but that's acceptable since there are no parameters to explain. It implies retrieval of projects but doesn't specify any filtering or options, which aligns with the empty schema.

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 ('projects from Linear'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'linear_getProjectIssues' or 'linear_getIssues', which also retrieve lists of Linear resources, so it doesn't achieve full 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. With sibling tools like 'linear_getProjectIssues' (which retrieves issues within projects) and 'linear_getIssues' (which retrieves issues generally), there's no indication of whether this tool is for listing project metadata, filtering, or other specific use cases.

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