Skip to main content
Glama

linear_getTeams

Retrieve all teams from the Linear project management system to view organizational structure and team assignments.

Instructions

Get a list of teams from Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'linear_getTeams' tool. It wraps the call to linearService.getTeams() with error handling.
    export function handleGetTeams(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getTeams();
        } catch (error) {
          logError('Error getting teams', error);
          throw error;
        }
      };
    }
  • The tool schema definition for 'linear_getTeams', specifying input (no parameters) and output schema (array of teams with id, name, key, description, 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 handleGetTeams function as the 'linear_getTeams' tool handler in the registerToolHandlers map.
    linear_getTeams: handleGetTeams(linearService),
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 it 'gets a list,' implying a read-only operation, but doesn't mention any behavioral traits like pagination, rate limits, authentication needs, or what happens if no teams exist. This leaves significant gaps for a tool 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 with zero waste. It is appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary details.

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 has 0 parameters, no annotations, and no output schema, the description is minimally adequate. It explains what the tool does but lacks details on return values or behavioral context, making it incomplete for full agent understanding without additional inference.

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 the schema fully documents the lack of parameters. The description doesn't add parameter-specific information, but with no parameters, this is acceptable, and it implies no filtering or options are needed, aligning with the 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') and resource ('list of teams from Linear'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'linear_getUsers' or 'linear_getProjects', which follow the same pattern, 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. There are no explicit when/when-not instructions or references to sibling tools, leaving usage context implied at best.

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/tacticlaunch/mcp-linear'

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