Skip to main content
Glama
Slack MCP Server

Slack MCP Server

by ubie-oss

slack_search_users

Search for Slack users by partial match on username, display name, or real name. Specify a query to find matching users, with optional limit and bot inclusion.

Instructions

Search for users by partial name match across username, display name, and real name. Use this when you need to find users containing specific keywords in their names. Returns up to the specified limit of matching users.

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": "slack_search_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of users to return (default 20)
queryYesSearch users by name, display name, or real name (partial match, case-insensitive)
include_botsNoInclude bot users in results (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses partial matching and the limit behavior, but does not mention that bots are excluded by default (include_bots defaults to false) or return format. Adequate but could be more detailed.

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?

Two sentences with no unnecessary words. Front-loaded with the action and immediate context. Highly efficient.

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?

With 3 parameters, full schema coverage, and no output schema, the description explains the search behavior and limit. It does not mention return format or error handling, but is fairly complete for a simple search tool.

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%, so baseline 3 is appropriate. The description reinforces what the query parameter does but adds no additional details about limit or include_bots beyond the schema.

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 states it searches for users by partial name match across username, display name, and real name. This distinguishes it from sibling tools like slack_get_users (which likely returns all users) and slack_search_channels (channels).

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

Usage Guidelines4/5

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

It explicitly says 'Use this when you need to find users containing specific keywords in their names,' providing clear context. It does not explicitly state when not to use alternatives, but the purpose is sufficiently differentiated.

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