Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Ai Automation Slack Channels

list_ai_automation_slack_channels
Read-only

Retrieve Slack channels synced from your connected workspace to use as automation destinations. Search by name to find channel IDs, limited to channels you can access.

Instructions

Channels Rootly has synced from the team's connected Slack workspace; any returned slack_channel_id is accepted as destination_slack_channel_id. When filter[search] is set, exact channel-name matches come first. When Slack channel user filtering is enabled, personal keys and OAuth tokens only see, and can only set new, channels the user can access in Slack; an update may resend the automation's current channel unchanged.

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_channels"
  }
}

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.3/5.0
Behavior4/5

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

Beyond the read-only and open-world annotations, the description discloses meaningful behavior: only synced channels are returned, search puts exact name matches first, and Slack user filtering can restrict visibility and newly settable channels. The note that an update may resend the automation's current channel unchanged is somewhat confusing in a list-tool description, but it does add behavioral context.

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

Conciseness3/5

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

The description is reasonably sized and front-loads the resource scope, but it is dense and not structured as a direct action statement. The final clause about updates resending the current channel is hard to parse and feels tangential for a listing tool.

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?

The description covers what the tool lists, search ordering, and permission-related filtering, which is useful. However, it omits pagination semantics for page_size and page_number and does not clearly state when the tool should be chosen over sibling Slack user/group listing tools.

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 must carry parameter meaning. It adds some semantics for search ordering via 'filter[search]', but it does not explain page_size or page_number, and the bracketed parameter name does not exactly match the schema's filter_search field.

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 identifies the resource: Slack channels synced by Rootly from the team's connected workspace. It does not use an explicit list verb, but the resource scope and the note that returned slack_channel_id values are accepted as destination_slack_channel_id make the purpose clear enough to distinguish it from sibling user/group listing tools.

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?

Usage is implied through the destination_slack_channel_id note: this is for finding Slack channels usable as automation destinations. However, there is no explicit when-to-use guidance, no mention of alternatives, and no clear statement about when to use search versus unfiltered listing.

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