Skip to main content
Glama

linear_getUsers

Retrieve a list of users from your Linear organization to manage team members and assign tasks effectively.

Instructions

Get a list of users in the Linear organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the linear_getUsers tool by calling linearService.getAllUsers() and handles errors.
    export function handleGetUsers(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getAllUsers();
        } catch (error) {
          logError('Error getting users', error);
          throw error;
        }
      };
    }
  • Schema definition for the linear_getUsers tool, specifying no input and array of user objects as output.
    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' },
          },
        },
      },
    };
  • Registration of the linear_getUsers handler in the tool handlers map, along with other user-related tools.
    // User tools
    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 ('Get a list') but does not describe any behavioral traits, such as whether it requires authentication, has rate limits, returns paginated results, or what format the output takes. This is a significant gap for a tool with no structured safety or operational hints.

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 that directly states the tool's purpose without any unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 for effective tool use. It does not explain what the returned list includes (e.g., user attributes, pagination details) or any operational constraints. For a tool that retrieves organizational data, more context on behavior and output is needed to guide the agent adequately.

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 the input schema has 100% description coverage (though empty). The description does not need to add parameter semantics, as there are none to document. A baseline score of 4 is appropriate since the schema fully covers the absence of parameters, and the description does not introduce any confusion.

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 immediately understandable. However, it does not differentiate this tool from potential sibling tools like 'linear_getViewer' or 'linear_getTeams', which also retrieve user-related data but with different scopes.

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 does not mention any prerequisites, exclusions, or context for usage, such as whether it retrieves all users, active users only, or if there are filtering options. This leaves the agent without direction on appropriate scenarios for invocation.

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