Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_getUsers

Retrieve a list of users from your Linear organization to manage team access and assign tasks within the project management system.

Instructions

Get a list of users in the Linear organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'linear_getUsers' tool. It wraps the call to linearService.getAllUsers() in an async function with error handling.
    export function handleGetUsers(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getAllUsers();
        } catch (error) {
          logError("Error getting users", error);
          throw error;
        }
      };
    }
  • Tool schema definition specifying the name, description, empty input schema, and output schema as an array of user objects.
    export const getUsersToolDefinition: MCPToolDefinition = {
      name: "linear_getUsers",
      description: "Get a list of users in the Linear organization",
      input_schema: {
        type: "object",
        properties: {},
      },
      output_schema: {
        type: "array",
        items: {
          type: "object",
          properties: {
            id: { type: "string" },
            name: { type: "string" },
            email: { type: "string" },
            displayName: { type: "string" },
            active: { type: "boolean" }
          }
        }
      }
    };
  • Tool registration within the registerToolHandlers function, mapping 'linear_getUsers' to the handleGetUsers handler.
    linear_getViewer: handleGetViewer(linearService),
    linear_getOrganization: handleGetOrganization(linearService),
    linear_getUsers: handleGetUsers(linearService),
    linear_getLabels: handleGetLabels(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 the action but doesn't describe traits like pagination, rate limits, authentication needs, or return format. This leaves significant gaps for a tool that likely involves network calls and data retrieval.

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 action and resource, making it easy to understand at a glance.

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 address behavioral aspects like response format, error handling, or usage constraints, which are important for a tool that retrieves organizational data.

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 tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this case is 4, as the description doesn't need to compensate for any parameter gaps, but it doesn't add extra semantic value beyond 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 verb ('Get') and resource ('list of users in the Linear organization'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'linear_getViewer' or 'linear_getOrganization', which also retrieve user/organization data, so it doesn't reach the highest 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. It doesn't mention prerequisites, context, or exclusions, such as whether this is for listing all users versus filtered subsets available in other tools like 'linear_getTeams'.

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