Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Create Ai Automation

create_ai_automation

Creates a saved AI agent automation that runs a prompt on schedules, incidents, alerts, Slack messages, webhooks, or on demand and posts results to Slack or the incident timeline.

Instructions

Create an AI automation. Set name and prompt; triggers decide when it runs, destination_kind where its answer is posted, and allowed_tool_keys which tools the agent may use (null means every tool the team allows, so pass an explicit list to keep it narrow). New automations are disabled unless enabled is true. 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:write. Read-only attributes are ignored on write.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "data": "<data>"
    },
    "name": "create_ai_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the generic annotations, it discloses the required OAuth write scope, disabled-by-default state, runtime tool restrictions and the broader access implied by null, answer-posting behavior, and handling of read-only attributes. These details communicate important authorization and safety consequences without conflicting with 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.

Conciseness4/5

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

The action and core configuration are front-loaded, and the authentication requirement is easy to locate. The allowed_tool_keys and destination behavior is substantially repeated across the first two paragraphs, so tightening the wording and moving the resource definition earlier would improve the structure.

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?

For this complex create operation, the description, detailed nested schema, annotations, and output schema collectively support a basic valid call and explain the major runtime effects. Explicit create-versus-update/run guidance and a pointer to get_ai_automation_trigger_options for source-specific conditions would improve discoverability, but their absence does not make the definition inadequate.

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

Parameters4/5

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

Despite the reported 0% schema-description coverage, the description compensates for the core fields by identifying name and prompt as required and explaining the roles of triggers, destination_kind, allowed_tool_keys, and enabled. It does not explain the top-level data/attributes envelope or fixed type value, while advanced scheduling, condition, limit, and Slack configuration remains entirely dependent on the nested schema.

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 opening verb and resource are explicit, and defining an automation as a saved prompt run by a Rootly AI agent makes the resource concrete. It does not explicitly distinguish creation from updating an automation, running one, or creating an AI skill.

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

Usage Guidelines4/5

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

It gives clear usage context: create a saved instruction that can run on a schedule, on matching incident, alert, Slack, or webhook events, or on demand. It provides no exclusions or explicit routing to alternatives such as update_ai_automation, run_ai_automation, 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