Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_getTeams

Retrieve a list of teams from Linear's project management system to support team operations and project setup.

Instructions

Get a list of teams from Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that implements the core logic for the linear_getTeams tool by calling linearService.getTeams().
    export function handleGetTeams(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getTeams();
        } catch (error) {
          logError("Error getting teams", error);
          throw error;
        }
      };
    } 
  • Tool schema definition including input (empty) and output schema for teams list with id, name, key, description, and states.
    export const getTeamsToolDefinition: MCPToolDefinition = {
      name: "linear_getTeams",
      description: "Get a list of teams from Linear",
      input_schema: {
        type: "object",
        properties: {},
      },
      output_schema: {
        type: "array",
        items: {
          type: "object",
          properties: {
            id: { type: "string" },
            name: { type: "string" },
            key: { type: "string" },
            description: { type: "string" },
            states: {
              type: "array",
              items: {
                type: "object",
                properties: {
                  id: { type: "string" },
                  name: { type: "string" }
                }
              }
            }
          }
        }
      }
    }; 
  • Registration of the linear_getTeams handler within the registerToolHandlers function.
    // Team tools
    linear_getTeams: handleGetTeams(linearService),
    linear_getWorkflowStates: handleGetWorkflowStates(linearService),
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 states the action is 'Get,' implying a read operation, but lacks details on permissions, rate limits, pagination, or return format. This is inadequate for a tool with zero 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 with no wasted words. It's front-loaded with the core purpose, making it easy to parse and understand quickly, which is ideal for 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the returned list includes (e.g., team fields, structure), behavioral traits like pagination, or error handling, leaving significant gaps for agent usage.

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% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it also doesn't compensate for any gaps since there are none, warranting a high baseline score.

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') and resource ('list of teams from Linear'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'linear_getUsers' or 'linear_getProjects' beyond the resource type, which prevents a perfect score.

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_getUsers' and 'linear_getProjects' available, there's no indication of use cases, prerequisites, or distinctions, leaving the agent without contextual direction.

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