Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Ai Automation Slack Users

list_ai_automation_slack_users
Read-only

Lists Slack users, including bots, from the connected workspace and returns IDs accepted by user and item_user trigger conditions.

Instructions

Users, including bots, from the team's connected Slack workspace; any returned slack_user_id is accepted by user and item_user trigger conditions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ai_automation_slack_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_sizeNo
page_numberNo
filter_searchNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds real value by disclosing that bots are included and that returned IDs are valid trigger inputs. It says nothing about pagination behavior or result-set size, which matters given the paging parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with no filler, and the resource-scoping fact is front-loaded followed by the trigger-compatibility note. The sentence-fragment form is slightly clipped but not ambiguous.

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?

An output schema exists, so return values need not be explained. However, with three undocumented parameters and no differentiation from sibling user-listing tools, the definition leaves real gaps an agent must resolve by trial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three parameters (page_size, page_number, filter_search), so the description carries the full burden and adds nothing — no paging defaults, no explanation of what filter_search matches against (name, email, bot/human?). An agent must guess the semantics.

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 names the resource precisely ('Users, including bots, from the team's connected Slack workspace') and adds a meaningful scope detail (bots are included). It does not, however, distinguish this from sibling listers such as list_users, list_schedule_rotation_users, or list_ai_automation_slack_user_groups, so the agent must infer which user list to call.

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

Usage Guidelines3/5

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

It implies usage by stating that returned slack_user_id values are accepted by 'user' and 'item_user' trigger conditions, which tells the agent this is the right source for trigger configuration. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for other user-listing needs.

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

Deploy Server

Other Tools