Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Ai Automation Slack User Groups

list_ai_automation_slack_user_groups
Read-only

Retrieves Slack user groups from the connected workspace and returns IDs accepted by user-group trigger conditions.

Instructions

User groups from the team's connected Slack workspace, read live from Slack; any returned slack_user_group_id is accepted by usergroup 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_user_groups"
  }
}

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 cover the safety profile (readOnly, non-destructive, open-world). The description adds two genuinely useful facts beyond them: results are read live from Slack rather than cached, and there is a prerequisite of a connected Slack workspace. It says nothing about pagination or the volume of results.

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 the resource and provenance front-loaded and no filler. The semicolon clause is dense but earns its place by linking IDs to trigger conditions.

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, and the Slack-connection precondition is stated. However, for a paginated list endpoint, the absence of any paging or search semantics leaves an agent guessing at how to retrieve a complete set of groups.

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%, so the description carries the full burden for page_size, page_number and filter_search, and it mentions none of them. In particular it is unclear whether filter_search matches group name, handle, or ID, which materially affects how an agent should call it.

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?

States a specific resource (user groups) and provenance ('from the team's connected Slack workspace, read live from Slack'), which separates it from the Slack channels and users siblings. The verb is implied by the name rather than stated, so it stops short of a full 5.

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?

The clause 'any returned slack_user_group_id is accepted by usergroup trigger conditions' tells the agent what the IDs are good for, which implies when to call it. There is no explicit guidance on when to prefer this over list_ai_automation_slack_users or get_ai_automation_trigger_options.

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