Skip to main content
Glama

get_users

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

Instructions

Get a list of users in the Linear workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that fetches all users from the Linear workspace using the LinearClient, formats them into a list with id, name, email, displayName, and active status, and returns them as a JSON string in the MCP content format.
    private async handleGetUsers() {
      const users = await linearClient.users();
      
      const formattedUsers = users.nodes.map(user => ({
        id: user.id,
        name: user.name,
        email: user.email,
        displayName: user.displayName,
        active: user.active,
      }));
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(formattedUsers, null, 2),
          },
        ],
      };
    }
  • src/index.ts:100-107 (registration)
    Registration of the 'get_users' tool in the listTools response, including its name, description, and input schema (no required parameters).
    {
      name: 'get_users',
      description: 'Get a list of users in the Linear workspace',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for the get_users tool, defined as an empty object (no parameters required).
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Dispatch case in the CallToolRequest handler that routes 'get_users' tool calls to the handleGetUsers method.
    case 'get_users':
      return await this.handleGetUsers();
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get a list' implies a read operation, it doesn't specify whether this requires authentication, returns paginated results, includes all users or filtered subsets, or has rate limits. The description is minimal and lacks important behavioral context.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple retrieval tool with no parameters and gets straight to the point.

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?

For a zero-parameter list retrieval tool with no output schema, the description is adequate but minimal. It covers the basic purpose but lacks important context about authentication requirements, result format, pagination, or how it differs from sibling tools. The absence of annotations means more behavioral detail would be helpful.

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 zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't mention parameters since none exist, maintaining focus on the tool's purpose without unnecessary detail.

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 ('users in the Linear workspace'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from potential sibling tools like get_tasks or get_teams, which would require mentioning what makes user retrieval unique.

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's no mention of prerequisites, context for user retrieval, or comparison to sibling tools like get_tasks or get_teams that might serve different purposes in the workspace.

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