Slack_connect

Slack List Users

slack_list_users

Read-onlyIdempotent

List users in the Slack workspace. Returns user profiles, IDs, and status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max number of users to return (default 100, max 1000)
`cursor`	No	Pagination cursor for next page of results

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	Whether the API call succeeded
`error`	No	Error code if API call failed
`members`	No	List of user objects
`message`	No	Error message or connection message
`response_metadata`	No	Pagination metadata

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Error code if API call failed",
+      "type": "string"
+    },
+    "members": {
+      "description": "List of user objects",
+      "items": {
+        "properties": {
+          "deleted": {
+            "description": "Whether user is deactivated",
+            "type": "boolean"
+          },
+          "id": {
+            "description": "User ID",
+            "type": "string"
+          },
+          "is_admin": {
+            "description": "Whether user is workspace admin",
+            "type": "boolean"
+          },
+          "is_bot": {
+            "description": "Whether this is a bot user",
+            "type": "boolean"
+          },
+          "is_owner": {
+            "description": "Whether user is workspace owner",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "User's display name",
+            "type": "string"
+          },
+          "profile": {
+            "description": "User profile information",
+            "properties": {
+              "display_name": {
+                "description": "User's display name",
+                "type": "string"
+              },
+              "email": {
+                "description": "User's email address",
+                "type": "string"
+              },
+              "real_name": {
+                "description": "User's real name",
+                "type": "string"
+              },
+              "status_emoji": {
+                "description": "User's status emoji",
+                "type": "string"
+              },
+              "status_text": {
+                "description": "User's status message",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "team_id": {
+            "description": "Workspace ID",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "description": "Error message or connection message",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the API call succeeded",
+      "type": "boolean"
+    },
+    "response_metadata": {
+      "description": "Pagination metadata",
+      "properties": {
+        "next_cursor": {
+          "description": "Cursor for next page of results",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 50
+  },
+  {
+    "cursor": "dXNlcl9pZDpVMDEyMzQ1Njc4OQ==",
+    "limit": 100
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds that it returns 'user profiles, IDs, and status,' which is not in the annotations.

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?

Single, front-loaded sentence with no filler. Every word provides value.

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?

The description covers purpose and return content. Missing mention of pagination, but schema handles it. With rich annotations and output schema, description is adequate.

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% and describes both parameters (limit, cursor) with clear details. Description adds no further parameter meaning, so baseline 3 applies.

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?

Description clearly states verb 'List' and resource 'users in the Slack workspace,' and differentiates from sibling tools like slack_list_channels and slack_send_message.

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?

No guidance on when to use this tool vs. alternatives (e.g., search_within, entity_profile) or when not to use it.

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

All Slack_connect tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.