Skip to main content
Glama

get_teams

Retrieve all teams from your Linear workspace to manage projects and assign tasks effectively.

Instructions

Get a list of teams in the Linear workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_teams' tool. Fetches all teams from the Linear workspace using the LinearClient, formats them into a simple object with id, name, key, and description, and returns the JSON stringified list as text content.
    private async handleGetTeams() {
      const teams = await linearClient.teams();
      
      const formattedTeams = teams.nodes.map(team => ({
        id: team.id,
        name: team.name,
        key: team.key,
        description: team.description,
      }));
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(formattedTeams, null, 2),
          },
        ],
      };
    }
  • The schema definition for the 'get_teams' tool, registered in the ListTools response. It has no input parameters.
    {
      name: 'get_teams',
      description: 'Get a list of teams in the Linear workspace',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:118-119 (registration)
    The switch case that registers and dispatches to the 'get_teams' handler when the tool is called.
    case 'get_teams':
      return await this.handleGetTeams();
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 states the tool retrieves a list but doesn't specify details like pagination, rate limits, authentication needs, or what 'list' entails (e.g., format, completeness). This leaves significant gaps for an agent to understand how to use it effectively.

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, effectively front-loading the purpose. It's appropriately sized for a simple tool with no parameters, making it 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, no annotations), the description is minimally adequate but lacks depth. It doesn't explain what the output looks like (e.g., list format, fields) or any behavioral traits, which could hinder an agent's ability to use it correctly without additional context.

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 there's no need for parameter details in the description. The description appropriately avoids discussing parameters, earning a high baseline score for not adding unnecessary information.

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 ('teams in the Linear workspace'), providing a specific purpose. However, it doesn't distinguish this from sibling tools like 'get_users' or 'get_tasks' 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 like 'get_users' or 'get_tasks', nor does it mention any context or prerequisites for usage. It merely states what the tool does without operational 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/Tyru5/linear-mcp'

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