linear-mcp-lean

Get team

get_team

Retrieve a team from Linear by providing its UUID, key (e.g., ENG), or name. Returns minimal data including id, name, and key.

Instructions

Get one team by id, key, or name → {id, name, key}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "get_team"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Team UUID, key (e.g. ENG), or name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description partially covers behavioral traits by indicating it returns a team object with selected fields. However, it does not mention error conditions, rate limits, or data freshness, leaving some transparency gaps.

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, front-loaded sentence that conveys purpose, inputs, and output without waste. Every word is necessary and effective.

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

Completeness4/5

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

For a simple one-parameter retrieval tool without an output schema, the description gives essential information. Minor improvement could be clarifying that the team is returned uniquely, but overall it is sufficiently complete.

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 coverage is 100% and the description restates the parameter 'query' as used for id, key, or name. No additional semantic value is added beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the action ('Get'), resource ('one team'), input options ('by id, key, or name'), and output structure ('{id, name, key}'). It effectively distinguishes from the sibling 'list_teams' by indicating it returns a single team.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving a specific team by identifier, but does not explicitly state when to use this tool versus alternatives like 'list_teams' or what to avoid. No context on prerequisites or exclusions is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.