Skip to main content
Glama

list_users

Retrieve a list of users from your Slack workspace to manage team members and access contact information.

Instructions

List users in the Slack workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of users to return

Implementation Reference

  • The handler function for the 'list_users' tool. It validates input args using listUsersSchema, calls the Slack users.list API with limit and cursor parameters, and returns members list and next_cursor.
    export async function listUsers(client: SlackClientWrapper, args: unknown) {
      const params = listUsersSchema.parse(args);
    
      return await client.safeCall(async () => {
        const result = await client.getClient().users.list({
          limit: params.limit,
          cursor: params.cursor,
        });
    
        return {
          members: result.members || [],
          next_cursor: result.response_metadata?.next_cursor,
        };
      });
    }
  • Zod schema used for input validation in the listUsers handler, defining optional limit and cursor parameters.
    export const listUsersSchema = z.object({
      limit: z.number().min(1).max(1000).optional().default(100),
      cursor: z.string().optional(),
    });
  • src/index.ts:122-136 (registration)
    Tool registration in the list_tools response: defines name 'list_users', description, and JSON inputSchema matching the Zod schema.
      name: 'list_users',
      description: 'List users in the Slack workspace',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of users to return',
            default: 100,
            minimum: 1,
            maximum: 1000,
          },
        },
      },
    },
  • src/index.ts:421-421 (registration)
    Handler binding in the toolHandlers map: maps 'list_users' calls to userTools.listUsers function with slackClient.
    list_users: (args) => userTools.listUsers(slackClient, args),
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this requires authentication, how results are returned (e.g., pagination), rate limits, or what data is included in the list, leaving significant 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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy 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. It doesn't explain what the list includes (e.g., user IDs, names, status), how results are structured, or any limitations, making it insufficient for a tool that likely returns complex user data.

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 description coverage is 100%, so the schema fully documents the 'limit' parameter. The description adds no additional parameter semantics beyond what's in the schema, resulting in the baseline score for adequate but not enhanced coverage.

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 ('List') and resource ('users in the Slack workspace'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_user_info' or 'invite_to_channel', 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_user_info' for specific user details or 'invite_to_channel' for user management. It lacks any context about use cases, prerequisites, or exclusions.

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/Hais/slack-bot-mcp'

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