Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Ai Automations

list_ai_automations
Read-only

List and filter a team's AI automations—prompts, triggers, destinations, allowed tools, run limits, and enabled status—to review scheduled, event-driven, or on-demand agent tasks.

Instructions

List the team's AI automations: name, prompt, triggers, destination, allowed tools, run limits and whether each is enabled. Read-only. An AI automation is a saved instruction (prompt) that a Rootly AI agent runs on a schedule, on a matching event (incident, alert, Slack message, webhook) or on demand. When it runs, the agent may only use the tools listed in the automation's allowed_tool_keys (all team-allowed tools when null), and it posts its answer to the configured destination (a Slack channel or the incident timeline), or nowhere when destination_kind is none.

Requires OAuth scope ai.automations:read.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
filter_searchNo
filter_enabledNo
filter_event_nameNoComma-separated values; any matching event name is included.
filter_trigger_kindNoComma-separated values; any matching trigger kind is included.
filter_created_at_gteNo
filter_created_at_lteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.7/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, and the description's "Read-only" merely restates that. Value beyond the annotations comes from the required OAuth scope `ai.automations:read` and from explaining semantics of returned data (null `allowed_tool_keys` means all team-allowed tools; `destination_kind` none means nowhere posted), which an agent needs to interpret 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?

The concrete listing scope is front-loaded in the first sentence, and the OAuth requirement closes the block. The middle definitional paragraph is long and partly reads as domain documentation rather than invocation guidance, but it does earn its place by clarifying triggers and destinations.

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 the absence of return-format detail is fine, and the auth scope covers a key prerequisite. However, with seven optional parameters at 29% coverage, an agent still lacks guidance on filtering, sorting, and default behavior — the main remaining gap for a filter-driven list tool.

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 coverage is only 29%: filter_search, filter_enabled, filter_created_at_gte/lte, and sort carry no schema descriptions, and the description says nothing about what they match, default sort order, or date-time expectations. The prose about `allowed_tool_keys` and `destination_kind` describes response fields, not the seven input parameters, so the low coverage gap is not compensated.

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 opens with a specific verb and resource ("List the team's AI automations") and enumerates the returned fields: name, prompt, triggers, destination, allowed tools, run limits, enabled state. The second paragraph defines what an AI automation actually is, so an agent knows the domain object it is listing rather than guessing from the name.

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 by "List the team's AI automations" and the filter-oriented schema, but the description never says when to use this versus get_ai_automation, list_ai_automation_runs, or run_ai_automation. No exclusions or prerequisite conditions are stated beyond the OAuth scope, so the agent must infer routing from tool names.

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