> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Rootly

The Rootly connector lets your AI agent act in each user's Rootly account. Each user connects their own Rootly access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 110 tools.

**Authentication:** Bearer Token
**Categories:** Monitoring, Developer Tools
**Tools:** 110: 73 read, 34 write, 3 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=ROOTLY)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Rootly connection

   In **AgentKit > Connections**, create a Rootly connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'rootly'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Rootly:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'rootly_get_current_user',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "rootly"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Rootly:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="rootly_get_current_user",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Rootly credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'rootly_get_action_item',
  toolInput: {
    id: '<id>',
  },
  connector: 'rootly',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="rootly_get_action_item",
    tool_input={
        "id": "<id>",
    },
    connection_name="rootly",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `rootly_get_action_item`

Get Action Item · Read-only

Retrieve an incident action item.
Returns the incident_action_item record with id, type and attributes (summary, description, kind, assigned_to, assigned_to_group_ids, priority).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_alert`

Get Alert · Read-only

Retrieve an alert.
Returns the alert record with id, type and attributes (short_id, noise, source, status, summary, description).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: environments,services,groups Comma-separated list of related resources to include: environments, services, groups, functionalities, responders, incidents, notified_users, events, alert_urgency, heartbeat, live_call_router, alert_group, group_leader_alert, group_member_alerts, alert_field_values, alerting_targets, escalation_policies, alert_call_recording. Example: services,environments.

Example input: `{"id":"<id>"}`

### `rootly_get_alert_group`

Get Alert Group · Read-only

Retrieve an alert group.
Returns the alert_group record with id, type and attributes (name, description, slug, condition_type, time_window, group_by_alert_title).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_alert_route`

Get Alert Route · Read-only

Get an alert route.
Returns the alert_route record with id, type and attributes (name, enabled, alerts_source_ids, owning_team_ids, rules).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `show_nested_ids` (`boolean`, optional): Include the IDs of nested destinations, condition groups and conditions, for referencing them in PATCH updates or deletions. Example: true.

Example input: `{"id":"<id>"}`

### `rootly_get_alert_source`

Get Alert Source · Read-only

Retrieve an alert source.
Returns the alert_source record with id, type and attributes (name, enabled, source_type, alert_urgency_id, deduplicate_alerts_by_key, deduplication_key_kind).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_alert_urgency`

Get Alert Urgency · Read-only

Retrieve an alert urgency.
Returns the alert_urgencie record with id, type and attributes (name, description, position, retrigger_timeout_minutes, urgency, color).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_catalog`

Get Catalog · Read-only

Retrieve a catalog.
Returns the catalog record with id, type and attributes (name, slug, description, icon, position, external_id).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_catalog_entity`

Get Catalog Entity · Read-only

Retrieve a Catalog Entity.
Returns the catalog_entitie record with id, type and attributes (name, slug, description, public_description, position, backstage_id).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: catalog,properties Comma-separated list of related resources to include: catalog, properties. Example: services,environments.

Example input: `{"id":"<id>"}`

### `rootly_get_cause`

Get Cause · Read-only

Retrieve a cause.
Returns the cause record with id, type and attributes (name, slug, description, public_description, position, properties).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_current_user`

Get Current User · Read-only

Get current user.
Returns the user record with id, type and attributes (email, first_name, last_name, full_name, full_name_with_team, time_zone).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `rootly_get_environment`

Get Environment · Read-only

Retrieve an environment.
Returns the environment record with id, type and attributes (name, slug, managed_by, external_id, description, public_description).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_escalation_policy`

Get Escalation Policy · Read-only

Retrieve an escalation policy.
Returns the escalation_policie record with id, type and attributes (name, description, repeat_count, created_by_user_id, last_updated_by_user_id, group_ids).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: escalation_policy_levels,escalation_policy_paths Comma-separated list of related resources to include: escalation_policy_levels, escalation_policy_paths, groups, services. Example: services,environments.

Example input: `{"id":"<id>"}`

### `rootly_get_functionality`

Get Functionality · Read-only

Retrieve a functionality.
Returns the functionalitie record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_incident`

Get Incident · Read-only

Retrieve an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: sub_statuses,causes,subscribers Comma-separated list of related resources to include: sub_statuses, causes, subscribers, roles, slack_messages, environments, incident_types, services, functionalities, groups, events, action_items, custom_field_selections, feedbacks, incident_post_mortem, alerts. Example: services,environments.

Example input: `{"id":"<id>"}`

### `rootly_get_incident_event`

Get Incident Event · Read-only

Retrieve an incident event.
Returns the incident_event record with id, type and attributes (event, visibility, occurred_at, created_at, updated_at).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_incident_role`

Get Incident Role · Read-only

Retrieve an incident role.
Returns the incident_role record with id, type and attributes (name, slug, summary, description, position, optional).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_incident_type`

Get Incident Type · Read-only

Retrieve an incident type.
Returns the incident_type record with id, type and attributes (name, slug, description, public_description, color, position).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_playbook`

Get Playbook · Read-only

Retrieve a playbook.
Returns the playbook record with id, type and attributes (title, summary, kind, content, external_url, severity_ids).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: severities,environments,services Comma-separated list of related resources to include: severities, environments, services, functionalities, groups, causes, incident_types. Example: services,environments.

Example input: `{"id":"<id>"}`

### `rootly_get_post_mortem`

Get Post Mortem · Read-only

Retrieve an incident retrospective.
Returns the incident_post_mortem record with id, type and attributes (title, content, status, started_at, mitigated_at, resolved_at).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_post_mortem_template`

Get Post Mortem Template · Read-only

Retrieve a Retrospective Template.
Returns the post_mortem_template record with id, type and attributes (name, slug, default, content, content_html, content_json).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_pulse`

Get Pulse · Read-only

Retrieve a pulse.
Returns the pulse record with id, type and attributes (source, summary, services, environments, external_url, labels).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_schedule`

Get Schedule · Read-only

Retrieve a schedule.
Returns the schedule record with id, type and attributes (name, description, all_time_coverage, time_zone, slack_user_group, slack_channel).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_service`

Get Service · Read-only

Retrieve a service.
Returns the service record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_severity`

Get Severity · Read-only

Retrieve a severity.
Returns the severitie record with id, type and attributes (name, slug, description, severity, color, position).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_status_page`

Get Status Page · Read-only

Retrieve a status page.
Returns the status_page record with id, type and attributes (title, slug, public_title, description, public_description, header_color).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_status_page_event`

Get Status Page Event · Read-only

Retrieve an incident status page event.
Returns the incident_status_page_event record with id, type and attributes (event, status_page_id, status, notify_subscribers, should_tweet, status_page_components).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_get_team`

Get Team · Read-only

Retrieve a team.
Returns the group record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: users Comma-separated list of related resources to include: users, schedules, escalation_policies. Example: services,environments.

Example input: `{"id":"<id>"}`

### `rootly_get_user`

Get User · Read-only

Retrieve an user.
Returns the user record with id, type and attributes (email, first_name, last_name, full_name, full_name_with_team, time_zone).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: email_addresses,phone_numbers Comma-separated list of related resources to include: email_addresses, phone_numbers, devices, role, on_call_role, teams, schedules, notification_rules. Example: services,environments.

Example input: `{"id":"<id>"}`

### `rootly_get_workflow`

Get Workflow · Read-only

Retrieve a workflow.
Returns the workflow record with id, type and attributes (name, slug, description, command, command_feedback_enabled, wait).
Use it when the id is known; use the matching list tool to find ids or filter.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: form_field_conditions,alert_field_conditions Comma-separated list of related resources to include: form_field_conditions, alert_field_conditions, genius_tasks, genius_workflow_runs. Example: services,environments.

Example input: `{"id":"<id>"}`

### `rootly_list_action_items`

List Action Items · Read-only

List all action items for an organization.
Returns a JSON:API list of incident_action_items with id, type and attributes (summary, description, kind, assigned_to, assigned_to_group_ids, priority); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_incident_status` (`string`, optional): Filter results by incident status. Example: Example filter incident status.
- `filter_kind` (`string`, optional): Filter results by kind. Example: Example filter kind.
- `filter_priority` (`string`, optional): Filter results by priority. Example: Example filter priority.
- `filter_status` (`string`, optional): Filter results by status. Example: Example filter status.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_alert_events`

List Alert Events · Read-only

List alert events.
Returns a JSON:API list of alert_events with id, type and attributes (alert_id, kind, action, page_reason, slack_message_ts, slack_message_permalink); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `alert_id` (`string`, required): The id (UUID) of the parent alert. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_action` (`string`, optional): Filter results by action. Example: Example filter action.
- `filter_kind` (`string`, optional): Filter results by kind. Example: Example filter kind.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"alert_id":"<alert_id>"}`

### `rootly_list_alert_groups`

List Alert Groups · Read-only

List alert groups.
Returns a JSON:API list of alert_groups with id, type and attributes (name, description, slug, condition_type, time_window, group_by_alert_title); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `include` (`string`, optional): The include value. Example: services,environments.

Example input: `{}`

### `rootly_list_alert_routes`

List Alert Routes · Read-only

List alert routes.
Returns a JSON:API list of alert_routes with id, type and attributes (name, enabled, alerts_source_ids, owning_team_ids, rules); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_alert_sources`

List Alert Sources · Read-only

List alert sources.
Returns a JSON:API list of alert_sources with id, type and attributes (name, enabled, source_type, alert_urgency_id, deduplicate_alerts_by_key, deduplication_key_kind); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_enabled` (`boolean`, optional): Filter results by enabled. Example: true.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_source_types` (`string`, optional): Filter results by source types. Example: Example filter source types.
- `filter_statuses` (`string`, optional): Filter results by statuses. Example: Example filter statuses.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_alert_urgencies`

List Alert Urgencies · Read-only

List alert urgencies.
Returns a JSON:API list of alert_urgencies with id, type and attributes (name, description, position, retrigger_timeout_minutes, urgency, color); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_alerts`

List Alerts · Read-only

List alerts.
Returns a JSON:API list of alerts with id, type and attributes (short_id, noise, source, status, summary, description); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_environments` (`string`, optional): Filter results by environments. Example: Example filter environments.
- `filter_groups` (`string`, optional): Filter results by groups. Example: Example filter groups.
- `filter_labels` (`string`, optional): Filter results by labels. Example: Example filter labels.
- `filter_services` (`string`, optional): Filter results by services. Example: Example filter services.
- `filter_source` (`string`, optional): Filter results by source. Example: Example filter source.
- `filter_status` (`string`, optional): Filter results by status. Example: Example filter status.
- `filter_updated_at_gte` (`string`, optional): Filter results by updated at gte. Example: Example filter updated at gte.
- `filter_updated_at_lte` (`string`, optional): Filter results by updated at lte. Example: Example filter updated at lte.
- `include` (`string`, optional): comma separated if needed. eg: environments,services,groups Comma-separated list of related resources to include: environments, services, groups, functionalities, responders, incidents, notified_users, events, alert_urgency, heartbeat, live_call_router, alert_group, group_leader_alert, group_member_alerts, alert_field_values, alerting_targets, escalation_policies, alert_call_recording. Example: services,environments.
- `page_after` (`string`, optional): The cursor to fetch results using cursor pagination. A cursor is provided in meta.next_cursor in the response. Example: Example page after.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_audits`

List Audits · Read-only

List audits.
Returns a JSON:API list of audits with id, type and attributes (event, event_display, item_type, item_type_display, object, object_changes); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_api_key_id` (`string`, optional): Filter results by api key id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_item_type` (`string`, optional): Filter results by item type. Example: Example filter item type.
- `filter_source` (`string`, optional): Filter results by source. Example: Example filter source.
- `filter_user_id` (`string`, optional): Filter results by user id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_catalog_entities`

List Catalog Entities · Read-only

List Catalog Entities.
Returns a JSON:API list of catalog_entities with id, type and attributes (name, slug, description, public_description, position, backstage_id); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `catalog_id` (`string`, required): The id (UUID) of the parent catalog. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_backstage_id` (`string`, optional): Filter results by backstage id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_external_id` (`string`, optional): Filter results by external id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_managed_by` (`string`, optional): Filter results by managed by. Example: Example filter managed by.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): comma separated if needed. eg: catalog,properties Comma-separated list of related resources to include: catalog, properties. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): comma separated if needed. eg: created_at,updated_at. One of: created_at, -created_at, updated_at, -updated_at, position, -position, name, -name. Example: created_at. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`, `position`, `-position`, `name`, `-name`.

Example input: `{"catalog_id":"<catalog_id>"}`

### `rootly_list_catalogs`

List Catalogs · Read-only

List catalogs.
Returns a JSON:API list of catalogs with id, type and attributes (name, slug, description, icon, position, external_id); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_external_id` (`string`, optional): Filter results by external id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_managed_by` (`string`, optional): Filter results by managed by. Example: Example filter managed by.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): comma separated if needed. eg: fields,entities Comma-separated list of related resources to include: fields, entities. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): comma separated if needed. eg: created_at,updated_at. One of: created_at, -created_at, updated_at, -updated_at, position, -position. Example: created_at. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`, `position`, `-position`.

Example input: `{}`

### `rootly_list_causes`

List Causes · Read-only

List causes.
Returns a JSON:API list of causes with id, type and attributes (name, slug, description, public_description, position, properties); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_environments`

List Environments · Read-only

List environments.
Returns a JSON:API list of environments with id, type and attributes (name, slug, managed_by, external_id, description, public_description); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_color` (`string`, optional): Filter results by color. Example: #6D55BD.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_escalation_levels`

List Escalation Levels · Read-only

List escalation levels for an Escalation Policy.
Returns a JSON:API list of resource with id, type and attributes (escalation_policy_id, escalation_policy_path_id, paging_strategy_configuration_strategy, paging_strategy_configuration_schedule_strategy, paging_strategy_configuration_repeats, paging_strategy_configuration_repeats_mode); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `escalation_policy_id` (`string`, required): The id (UUID) of the parent escalation policy. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"escalation_policy_id":"<escalation_policy_id>"}`

### `rootly_list_escalation_policies`

List Escalation Policies · Read-only

List escalation policies.
Returns a JSON:API list of escalation_policies with id, type and attributes (name, description, repeat_count, created_by_user_id, last_updated_by_user_id, group_ids); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_team_ids` (`string`, optional): Filter escalation policies by associated team IDs. Comma-separate multiple values. Example: Example filter team ids.
- `include` (`string`, optional): comma separated if needed. eg: escalation_policy_levels,escalation_policy_paths Comma-separated list of related resources to include: escalation_policy_levels, escalation_policy_paths, groups, services. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_functionalities`

List Functionalities · Read-only

List functionalities.
Returns a JSON:API list of functionalities with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_backstage_id` (`string`, optional): Filter results by backstage id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_cortex_id` (`string`, optional): Filter results by cortex id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_external_id` (`string`, optional): Filter results by external id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_opslevel_id` (`string`, optional): Filter results by opslevel id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_incident_action_items`

List Incident Action Items · Read-only

List incident action items.
Returns a JSON:API list of incident_action_items with id, type and attributes (summary, description, kind, assigned_to, assigned_to_group_ids, priority); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"incident_id":"<incident_id>"}`

### `rootly_list_incident_alerts`

List Incident Alerts · Read-only

List Incident alerts.
Returns a JSON:API list of alerts with id, type and attributes (short_id, noise, source, status, summary, description); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: environments,services,groups Comma-separated list of related resources to include: environments, services, groups, functionalities, responders, incidents, notified_users, events, alert_urgency, heartbeat, live_call_router, alert_group, group_leader_alert, group_member_alerts, alert_field_values, alerting_targets, escalation_policies, alert_call_recording. Example: services,environments.

Example input: `{"incident_id":"<incident_id>"}`

### `rootly_list_incident_events`

List Incident Events · Read-only

List incident events.
Returns a JSON:API list of incident_events with id, type and attributes (event, visibility, occurred_at, created_at, updated_at); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"incident_id":"<incident_id>"}`

### `rootly_list_incident_feedbacks`

List Incident Feedbacks · Read-only

List incident feedbacks.
Returns a JSON:API list of incident_feedbacks with id, type and attributes (feedback, rating, anonymous, created_at, updated_at); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"incident_id":"<incident_id>"}`

### `rootly_list_incident_roles`

List Incident Roles · Read-only

List incident roles.
Returns a JSON:API list of incident_roles with id, type and attributes (name, slug, summary, description, position, optional); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_enabled` (`boolean`, optional): Filter results by enabled. Example: true.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_incident_status_page_events`

List Incident Status Page Events · Read-only

List incident status page events.
Returns a JSON:API list of incident_status_page_events with id, type and attributes (event, status_page_id, status, notify_subscribers, should_tweet, status_page_components); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"incident_id":"<incident_id>"}`

### `rootly_list_incident_sub_statuses`

List Incident Sub Statuses · Read-only

List incident_sub_statuses.
Returns a JSON:API list of incident_sub_statuses with id, type and attributes (incident_id, sub_status_id, assigned_at, assigned_by_user_id); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_sub_status_id` (`string`, optional): Filter results by sub status id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): comma separated if needed. eg: sub_status,assigned_by_user Comma-separated list of related resources to include: sub_status, assigned_by_user. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): comma separated if needed. eg: created_at,updated_at. One of: created_at, -created_at, updated_at, -updated_at, assigned_at, -assigned_at. Example: created_at. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`, `assigned_at`, `-assigned_at`.

Example input: `{"incident_id":"<incident_id>"}`

### `rootly_list_incident_types`

List Incident Types · Read-only

List incident types.
Returns a JSON:API list of incident_types with id, type and attributes (name, slug, description, public_description, color, position); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_color` (`string`, optional): Filter results by color. Example: #6D55BD.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_incidents`

List Incidents · Read-only

List incidents.
Returns a JSON:API list of incidents with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_environment_ids` (`string`, optional): Filter results by environment ids. Example: Example filter environment ids.
- `filter_environments` (`string`, optional): Filter results by environments. Example: Example filter environments.
- `filter_functionalities` (`string`, optional): Filter results by functionalities. Example: Example filter functionalities.
- `filter_functionality_ids` (`string`, optional): Filter results by functionality ids. Example: Example filter functionality ids.
- `filter_functionality_names` (`string`, optional): Filter results by functionality names. Example: Example filter functionality names.
- `filter_kind` (`string`, optional): Filter results by kind. Example: Example filter kind.
- `filter_labels` (`string`, optional): Filter results by labels. Example: Example filter labels.
- `filter_private` (`string`, optional): Filter results by private. Example: Example filter private.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_service_ids` (`string`, optional): Filter results by service ids. Example: Example filter service ids.
- `filter_service_names` (`string`, optional): Filter results by service names. Example: Example filter service names.
- `filter_services` (`string`, optional): Filter results by services. Example: Example filter services.
- `filter_severity` (`string`, optional): Filter results by severity. Example: Example filter severity.
- `filter_severity_id` (`string`, optional): Filter results by severity id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_status` (`string`, optional): Filter results by status. Example: Example filter status.
- `filter_type_ids` (`string`, optional): Filter results by type ids. Example: Example filter type ids.
- `filter_types` (`string`, optional): Filter results by types. Example: Example filter types.
- `filter_user_id` (`integer`, optional): Filter results by user id. Example: 12345.
- `include` (`string`, optional): comma separated if needed. eg: sub_statuses,causes,subscribers Comma-separated list of related resources to include: sub_statuses, causes, subscribers, roles, slack_messages, environments, incident_types, services, functionalities, groups, events, action_items, custom_field_selections, feedbacks, incident_post_mortem, alerts. Example: services,environments.
- `page_after` (`string`, optional): The cursor to fetch results using cursor pagination. A cursor is provided in meta.next_cursor in the response. Example: Example page after.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): comma separated if needed. eg: created_at,updated_at. One of: created_at, -created_at, updated_at, -updated_at, started_at, -started_at, in_triage_at, -in_triage_at, mitigated_at, -mitigated_at, resolved_at, -resolved_at. Example: created_at. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`, `started_at`, `-started_at`, `in_triage_at`, `-in_triage_at`, `mitigated_at`, `-mitigated_at`, `resolved_at`, `-resolved_at`.

Example input: `{}`

### `rootly_list_live_call_routers`

List Live Call Routers · Read-only

List Live Call Routers.
Returns a JSON:API list of live_call_routers with id, type and attributes (kind, enabled, name, country_code, phone_type, phone_number); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_oncalls`

List Oncalls · Read-only

List on-calls.
Returns a JSON:API list of on_call_resources with id, type and attributes (escalation_policy_id, escalation_policy_name, escalation_policy_path_id, escalation_policy_path_name, notification_type, is_default_path); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `earliest` (`boolean`, optional): When true, returns only the first on-call entry per escalation policy path and level. Example: true.
- `filter_escalation_policy_ids` (`string`, optional): Comma-separated escalation policy IDs. Example: Example filter escalation policy ids.
- `filter_group_ids` (`string`, optional): Comma-separated group IDs (teams). Example: Example filter group ids.
- `filter_notification_types` (`string`, optional): Comma-separated notification types to include. One or both of: audible, quiet. When omitted, returns oncalls from all non-deferral escalation paths. When provided, limits results to matching notification types and sorts audible-first. Example: Example filter notification types.
- `filter_schedule_ids` (`string`, optional): Comma-separated schedule IDs. Example: Example filter schedule ids.
- `filter_service_ids` (`string`, optional): Comma-separated service IDs. Example: Example filter service ids.
- `filter_user_ids` (`string`, optional): Comma-separated user IDs. Example: Example filter user ids.
- `include` (`string`, optional): comma separated if needed. eg: user,schedule Comma-separated list of related resources to include: user, schedule, escalation_policy. Example: services,environments.
- `since` (`string`, optional): Start of time range in ISO-8601 format (e.g., 2025-01-01T00:00:00Z). Defaults to current time. Example: Example since.
- `time_zone` (`string`, optional): Timezone for response times (e.g., America/New_York). Defaults to UTC. Example: 2025-01-15T14:30:00Z.
- `until` (`string`, optional): End of time range in ISO-8601 format (e.g., 2025-01-01T00:00:00Z). Defaults to 'since' time. Example: Example until.

Example input: `{}`

### `rootly_list_playbooks`

List Playbooks · Read-only

List playbooks.
Returns a JSON:API list of playbooks with id, type and attributes (title, summary, kind, content, external_url, severity_ids); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `include` (`string`, optional): comma separated if needed. eg: severities,environments,services Comma-separated list of related resources to include: severities, environments, services, functionalities, groups, causes, incident_types. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_post_mortem_templates`

List Post Mortem Templates · Read-only

List Retrospective Templates.
Returns a JSON:API list of post_mortem_templates with id, type and attributes (name, slug, default, content, content_html, content_json); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_post_mortems`

List Post Mortems · Read-only

List incident retrospectives.
Returns a JSON:API list of incident_post_mortems with id, type and attributes (title, content, status, started_at, mitigated_at, resolved_at); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_cause_ids` (`string`, optional): Filter by cause IDs (UUIDs). Example: Example filter cause ids.
- `filter_causes` (`string`, optional): Filter by cause slugs. Example: Example filter causes.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_environment_ids` (`string`, optional): Filter by environment IDs (UUIDs). Example: Example filter environment ids.
- `filter_environments` (`string`, optional): Filter by environment slugs. Example: Example filter environments.
- `filter_functionalities` (`string`, optional): Filter by functionality slugs. Example: Example filter functionalities.
- `filter_functionality_ids` (`string`, optional): Filter by functionality IDs (UUIDs). Example: Example filter functionality ids.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_service_ids` (`string`, optional): Filter by service IDs (UUIDs). Example: Example filter service ids.
- `filter_services` (`string`, optional): Filter by service slugs. Example: Example filter services.
- `filter_severity` (`string`, optional): Filter results by severity. Example: Example filter severity.
- `filter_status` (`string`, optional): Filter results by status. Example: Example filter status.
- `filter_team_ids` (`string`, optional): Filter by team/group IDs (UUIDs). Example: Example filter team ids.
- `filter_teams` (`string`, optional): Filter by team/group slugs. Example: Example filter teams.
- `filter_type` (`string`, optional): Filter results by type. Example: Example filter type.
- `filter_type_ids` (`string`, optional): Filter by incident type IDs (UUIDs). Example: Example filter type ids.
- `filter_types` (`string`, optional): Filter by incident type slugs. Example: Example filter types.
- `filter_user_id` (`integer`, optional): Filter results by user id. Example: 12345.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_pulses`

List Pulses · Read-only

List pulses.
Returns a JSON:API list of pulses with id, type and attributes (source, summary, services, environments, external_url, labels); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_environments` (`string`, optional): Filter results by environments. Example: Example filter environments.
- `filter_labels` (`string`, optional): Filter results by labels. Example: Example filter labels.
- `filter_refs` (`string`, optional): Filter results by refs. Example: Example filter refs.
- `filter_services` (`string`, optional): Filter results by services. Example: Example filter services.
- `filter_source` (`string`, optional): Filter results by source. Example: Example filter source.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_schedule_override_shifts`

List Schedule Override Shifts · Read-only

List override shifts.
Returns a JSON:API list of shifts with id, type and attributes (schedule_id, rotation_id, starts_at, ends_at, is_override, created_at); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`string`, required): The id (UUID) of the parent schedule. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"schedule_id":"<schedule_id>"}`

### `rootly_list_schedule_shifts`

List Schedule Shifts · Read-only

Retrieve a schedule shifts.
Returns a JSON:API list of shifts with id, type and attributes (schedule_id, rotation_id, starts_at, ends_at, is_override, is_shadow); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `from` (`string`, optional): The from query value. Example: Example from.
- `to` (`string`, optional): The to query value. Example: Example to.

Example input: `{"id":"<id>"}`

### `rootly_list_schedules`

List Schedules · Read-only

List schedules.
Returns a JSON:API list of schedules with id, type and attributes (name, description, all_time_coverage, time_zone, slack_user_group, slack_channel); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_team_ids` (`string`, optional): Filter schedules by owning team IDs. Comma-separate multiple values. Example: Example filter team ids.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_services`

List Services · Read-only

List services.
Returns a JSON:API list of services with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_alert_broadcast_enabled` (`boolean`, optional): Filter results by alert broadcast enabled. Example: true.
- `filter_backstage_id` (`string`, optional): Filter results by backstage id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_cortex_id` (`string`, optional): Filter results by cortex id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_external_id` (`string`, optional): Filter results by external id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_incident_broadcast_enabled` (`boolean`, optional): Filter results by incident broadcast enabled. Example: true.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_opslevel_id` (`string`, optional): Filter results by opslevel id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_severities`

List Severities · Read-only

List severities.
Returns a JSON:API list of severities with id, type and attributes (name, slug, description, severity, color, position); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_color` (`string`, optional): Filter results by color. Example: #6D55BD.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_severity` (`string`, optional): Filter results by severity. Example: Example filter severity.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_shifts`

List Shifts · Read-only

List shifts.
Returns a JSON:API list of shifts with id, type and attributes (schedule_id, rotation_id, starts_at, ends_at, is_override, is_shadow); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `from` (`string`, optional): Start range for shifts in ISO-8601 format. When omitted with `to`, defaults to `to` for a point-in-time lookup; when both bounds are omitted, defaults to the current time through one month ahead. Example: Example from.
- `include` (`string`, optional): comma separated if needed. eg: shift_override,user. Note: `user` is deprecated, use `assignee` instead. Comma-separated list of related resources to include: shift_override, user, assignee, shift_shadow. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `schedule_ids_` (`array`, optional): The schedule ids query value. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `to` (`string`, optional): End range for shifts in ISO-8601 format. When omitted with `from`, defaults to `from`; when both bounds are omitted, defaults to the current time through one month ahead. Example: Example to.
- `user_ids_` (`array`, optional): The user ids query value. Example: [{"key": "value"}]

Example input: `{}`

### `rootly_list_status_page_announcements`

List Status Page Announcements · Read-only

List status page announcements.
Returns a JSON:API list of status_page_announcements with id, type and attributes (status_page_id, title, body, user_id, published_at, created_at); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `status_page_id` (`string`, required): The id (UUID) of the parent status page. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"status_page_id":"<status_page_id>"}`

### `rootly_list_status_page_components`

List Status Page Components · Read-only

List status page components.
Returns a JSON:API list of status_page_components with id, type and attributes (status_page_id, status_page_component_group_id, name, description, position, source_type); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `status_page_id` (`string`, required): The id (UUID) of the parent status page. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{"status_page_id":"<status_page_id>"}`

### `rootly_list_status_pages`

List Status Pages · Read-only

List status pages.
Returns a JSON:API list of status_pages with id, type and attributes (title, slug, public_title, description, public_description, header_color); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_statuses`

List Statuses · Read-only

List Statuses.
Returns a JSON:API list of statuses with id, type and attributes (name, slug, description, color, enabled, created_at); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_enabled` (`boolean`, optional): Filter results by enabled. Example: true.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_sub_statuses`

List Sub Statuses · Read-only

List Sub-Statuses.
Returns a JSON:API list of sub_statuses with id, type and attributes (name, slug, description, parent_status, position, created_at); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_parent_status` (`string`, optional): Filter results by parent status. Example: Example filter parent status.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): The include value. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.

Example input: `{}`

### `rootly_list_teams`

List Teams · Read-only

List teams.
Returns a JSON:API list of groups with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_alert_broadcast_enabled` (`boolean`, optional): Filter results by alert broadcast enabled. Example: true.
- `filter_backstage_id` (`string`, optional): Filter results by backstage id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_color` (`string`, optional): Filter results by color. Example: #6D55BD.
- `filter_cortex_id` (`string`, optional): Filter results by cortex id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_external_id` (`string`, optional): Filter results by external id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_incident_broadcast_enabled` (`boolean`, optional): Filter results by incident broadcast enabled. Example: true.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_opslevel_id` (`string`, optional): Filter results by opslevel id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): comma separated if needed. eg: users Comma-separated list of related resources to include: users, schedules, escalation_policies. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): The sort query value. Example: -created_at.

Example input: `{}`

### `rootly_list_users`

List Users · Read-only

List users.
Returns a JSON:API list of users with id, type and attributes (email, first_name, last_name, full_name, full_name_with_team, time_zone); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_email` (`string`, optional): Filter results by email. Example: oncall@example.com.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `include` (`string`, optional): comma separated if needed. eg: email_addresses,phone_numbers Comma-separated list of related resources to include: email_addresses, phone_numbers, devices, role, on_call_role, teams, schedules, notification_rules. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): comma separated if needed. eg: created_at,updated_at. One of: created_at, -created_at, updated_at, -updated_at. Example: created_at. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`.

Example input: `{}`

### `rootly_list_workflows`

List Workflows · Read-only

List workflows.
Returns a JSON:API list of workflows with id, type and attributes (name, slug, description, command, command_feedback_enabled, wait); use page_number and page_size to paginate.
Use it to browse or filter records; fetch one record by id with the matching get tool when the id is known.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `filter_created_at_gte` (`string`, optional): Filter results by created at gte. Example: Example filter created at gte.
- `filter_created_at_lte` (`string`, optional): Filter results by created at lte. Example: Example filter created at lte.
- `filter_name` (`string`, optional): Filter results by name. Example: Example filter name.
- `filter_search` (`string`, optional): Filter results by search. Example: database timeout.
- `filter_slug` (`string`, optional): Filter results by slug. Example: database-primary.
- `include` (`string`, optional): comma separated if needed. eg: form_field_conditions,alert_field_conditions Comma-separated list of related resources to include: form_field_conditions, alert_field_conditions, genius_tasks, genius_workflow_runs. Example: services,environments.
- `page_number` (`integer`, optional): Page number to fetch, starting at 1. Example: 1.
- `page_size` (`integer`, optional): Number of records per page (default 10). Example: 25.
- `sort` (`string`, optional): comma separated if needed. eg: created_at,updated_at. One of: created_at, -created_at, updated_at, -updated_at, position, -position. Example: created_at. One of: `created_at`, `-created_at`, `updated_at`, `-updated_at`, `position`, `-position`.

Example input: `{}`

### `rootly_acknowledge_alert`

Acknowledge Alert · Write

Acknowledge an alert.
Returns the alert record with id, type and attributes (short_id, noise, source, status, summary, description).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `actor` (`object`, optional): The user to record as performing this action. Only available when actor attribution is enabled for the organization; otherwise it is ignored. Only supported with Global and Team API keys; with a Team API key the user must belong to one of the key's teams. When omitted or null, the action is attributed to the API key. Otherwise provide either `email` or `user_id`, not both. Provide as a JSON object. Example: {"key": "value"}

Example input: `{"id":"<id>"}`

### `rootly_add_incident_subscribers`

Add Incident Subscribers · Write

Add subscribers to incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `remove_users_with_no_private_incident_access` (`boolean`, optional): Users without read permissions for private incidents will be removed from the subscriber list of this incident. Example: true.
- `user_ids` (`array`, optional): IDs of users you wish to add to list of subscribers for this incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]

Example input: `{"id":"<id>"}`

### `rootly_assign_incident_role`

Assign Incident Role · Write

Assign user to incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `incident_role_id` (`string`, optional): ID of the incident role. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `user_id` (`string`, optional): ID of user you wish to assign this incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_cancel_incident`

Cancel Incident · Write

Cancel an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `cancellation_message` (`string`, optional): Why was the incident cancelled?. Example: Elevated p99 latency on the checkout API.

Example input: `{"id":"<id>"}`

### `rootly_create_alert`

Create Alert · Write

Create an alert.
Returns the alert record with id, type and attributes (short_id, noise, source, status, summary, description).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `summary` (`string`, required): The summary of the alert. Example: Elevated p99 latency on the checkout API.
- `actor` (`object`, optional): The user to record as performing this action. Only available when actor attribution is enabled for the organization; otherwise it is ignored. Only supported with Global and Team API keys; with a Team API key the user must belong to one of the key's teams. When omitted or null, the action is attributed to the API key. Otherwise provide either `email` or `user_id`, not both. Provide as a JSON object. Example: {"key": "value"}
- `alert_field_values_attributes` (`array`, optional): Custom alert field values to create with the alert. Example: [{"key": "value"}]
- `alert_urgency_id` (`string`, optional): The ID of the alert urgency. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `data` (`object`, optional): Additional data. Provide as a JSON object. Example: {"key": "value"}
- `deduplication_key` (`string`, optional): Alerts sharing the same deduplication key are treated as a single alert. Example: OPS-123.
- `description` (`string`, optional): The description of the alert. Example: Elevated p99 latency on the checkout API.
- `ended_at` (`string`, optional): Alert end datetime. Example: 2025-01-15T14:30:00Z.
- `environment_ids` (`array`, optional): The Environment IDs to attach to the alert. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `external_id` (`string`, optional): External ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `external_url` (`string`, optional): External Url. Example: https://example.com/runbook.
- `functionality_ids` (`array`, optional): The Functionality IDs to attach to the alert. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `group_ids` (`array`, optional): The Group IDs to attach to the alert. If your organization has On-Call enabled and your notification target is a Group. This field will be automatically set for you. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `labels` (`array`, optional): The labels value. Example: [{"key": "value"}]
- `noise` (`string`, optional): Whether the alert is marked as noise. One of: noise, not_noise. Example: noise. One of: `noise`, `not_noise`.
- `notification_target_id` (`string`, optional): Only available for organizations with Rootly On-Call enabled. The _identifier_ of the notification target object. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `notification_target_type` (`string`, optional): Only available for organizations with Rootly On-Call enabled. Can be one of Group, Service, EscalationPolicy, Functionality, User. Please contact support if you encounter issues using `Functionality` as a notification target type. One of: User, Group, EscalationPolicy, Service, Functionality. Example: User. One of: `User`, `Group`, `EscalationPolicy`, `Service`, `Functionality`.
- `notification_targets` (`array`, optional): Only available for organizations with Rootly On-Call enabled. Page multiple destinations (any combination of Group, Service, EscalationPolicy, Functionality, or User) in a single request. `Functionality` targets require the `enable_paging_functionalities` feature; a request that includes one while it is disabled is rejected. Applies to alert creation only. When provided, this takes precedence over the singular `notification_target_type` / `notification_target_id` fields. Example: [{"key": "value"}]
- `service_ids` (`array`, optional): The Service IDs to attach to the alert. If your organization has On-Call enabled and your notification target is a Service. This field will be automatically set for you. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `source` (`string`, optional): Deprecated. Accepted for backwards compatibility; new clients should omit. Defaults to `api`. Example: Example source.
- `started_at` (`string`, optional): Alert start datetime. Example: 2025-01-15T14:30:00Z.
- `status` (`string`, optional): Only available for organizations with Rootly On-Call enabled. Can be one of open, triggered. One of: open, triggered. Example: open. One of: `open`, `triggered`.

Example input: `{"summary":"<summary>"}`

### `rootly_create_environment`

Create Environment · Write

Create an environment.
Returns the environment record with id, type and attributes (name, slug, managed_by, external_id, description, public_description).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the environment. Example: Checkout API latency.
- `color` (`string`, optional): The hex color of the environment. Example: #6D55BD.
- `description` (`string`, optional): The description of the environment. Example: Elevated p99 latency on the checkout API.
- `external_id` (`string`, optional): The external id associated to this environment. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `notify_emails` (`array`, optional): Emails to attach to the environment. Example: ["example"]
- `position` (`integer`, optional): Position of the environment. Example: 10.
- `properties` (`array`, optional): Array of property values for this environment. Example: [{"key": "value"}]
- `public_description` (`string`, optional): The status page description of the environment. Example: Elevated p99 latency on the checkout API.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this environment. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this environment. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.

Example input: `{"name":"<name>"}`

### `rootly_create_functionality`

Create Functionality · Write

Create a functionality.
Returns the functionalitie record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the functionality. Example: Checkout API latency.
- `backstage_id` (`string`, optional): The Backstage entity id associated to this functionality. eg: :namespace/:kind/:entity_name. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `color` (`string`, optional): The hex color of the functionality. Example: #6D55BD.
- `cortex_id` (`string`, optional): The Cortex group id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `description` (`string`, optional): The description of the functionality. Example: Elevated p99 latency on the checkout API.
- `environment_ids` (`array`, optional): Environments associated with this functionality. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `escalation_policy_id` (`string`, optional): The escalation policy id of the functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `external_id` (`string`, optional): The external id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `notify_emails` (`array`, optional): Emails to attach to the functionality. Example: ["example"]
- `opsgenie_id` (`string`, optional): The Opsgenie service id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `opsgenie_team_id` (`string`, optional): The Opsgenie team id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `owner_group_ids` (`array`, optional): Owner Teams associated with this functionality. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `owner_user_ids` (`array`, optional): Owner Users associated with this functionality. Example: [{"key": "value"}]
- `pagerduty_id` (`string`, optional): The PagerDuty service id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `position` (`integer`, optional): Position of the functionality. Example: 10.
- `properties` (`array`, optional): Array of property values for this functionality. Example: [{"key": "value"}]
- `public_description` (`string`, optional): The status page description of the functionality. Example: Elevated p99 latency on the checkout API.
- `service_ids` (`array`, optional): Services associated with this functionality. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `service_now_ci_sys_id` (`string`, optional): The Service Now CI sys id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `show_uptime` (`boolean`, optional): Show uptime. Example: 2025-01-15T14:30:00Z.
- `show_uptime_last_days` (`integer`, optional): Show uptime over x days. Example: 2025-01-15T14:30:00Z.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this functionality. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this functionality. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.

Example input: `{"name":"<name>"}`

### `rootly_create_incident`

Create Incident · Write

Create an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `acknowledged_at` (`string`, optional): Date of acknowledgment. Example: 2025-01-15T14:30:00Z.
- `alert_ids` (`array`, optional): The Alert IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `cancelled_at` (`string`, optional): Date of cancellation. Example: 2025-01-15T14:30:00Z.
- `cause_ids` (`array`, optional): The Cause IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `closed_at` (`string`, optional): Date of closure. Example: 2025-01-15T14:30:00Z.
- `detected_at` (`string`, optional): Date of detection. Example: 2025-01-15T14:30:00Z.
- `duplicate_incident_id` (`string`, optional): ID of duplicated incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `environment_ids` (`array`, optional): The Environment IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `functionality_ids` (`array`, optional): The Functionality IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `google_drive_parent_id` (`string`, optional): Google Drive parent folder ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `google_drive_url` (`string`, optional): Google Drive URL. Example: https://example.com/runbook.
- `group_ids` (`array`, optional): The Team IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `in_triage_at` (`string`, optional): Date of triage. Example: 2025-01-15T14:30:00Z.
- `incident_type_ids` (`array`, optional): The Incident Type IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `jira_issue_id` (`string`, optional): Jira issue ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `jira_issue_key` (`string`, optional): Jira issue key. Example: OPS-123.
- `jira_issue_url` (`string`, optional): Jira issue URL. Example: https://example.com/runbook.
- `kind` (`string`, optional): The kind of the incident. One of: test, test_sub, example, example_sub, normal, normal_sub, backfilled, scheduled, scheduled_sub. Example: test. One of: `test`, `test_sub`, `example`, `example_sub`, `normal`, `normal_sub`, `backfilled`, `scheduled`, `scheduled_sub`.
- `labels` (`object`, optional): Labels to attach to the incidents. eg: {"platform":"osx", "version": "1.29"}. Provide as a JSON object. Example: {"key": "value"}
- `linear_issue_id` (`string`, optional): Linear issue ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `linear_issue_key` (`string`, optional): Linear issue key. Example: OPS-123.
- `linear_issue_url` (`string`, optional): Linear issue URL. Example: https://example.com/runbook.
- `mitigated_at` (`string`, optional): Date of mitigation. Example: 2025-01-15T14:30:00Z.
- `muted_service_ids` (`array`, optional): The Service IDs to mute alerts for during maintenance. Alerts for these services will still be triggered and attached to the incident, but won't page responders. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `notify_emails` (`array`, optional): Emails you want to notify. Example: ["example"]
- `parent_incident_id` (`string`, optional): ID of parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `private` (`boolean`, optional): Create an incident as private. Once an incident is made as private it cannot be undone. Example: true.
- `public_title` (`string`, optional): The public title of the incident. Example: Checkout API latency.
- `resolved_at` (`string`, optional): Date of resolution. Example: 2025-01-15T14:30:00Z.
- `scheduled_for` (`string`, optional): Date of when the maintenance begins. Example: Example scheduled for.
- `scheduled_until` (`string`, optional): Date of when the maintenance ends. Example: Example scheduled until.
- `service_ids` (`array`, optional): The Service IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `severity_id` (`string`, optional): The Severity ID to attach to the incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `slack_channel_archived` (`boolean`, optional): Whether the Slack channel is archived. Example: true.
- `slack_channel_id` (`string`, optional): Slack channel id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `slack_channel_name` (`string`, optional): Slack channel name. Example: Example slack channel name.
- `slack_channel_url` (`string`, optional): Slack channel url. Example: https://example.com/runbook.
- `started_at` (`string`, optional): Date of start. Example: 2025-01-15T14:30:00Z.
- `status` (`string`, optional): The status of the incident. One of: in_triage, started, detected, acknowledged, mitigated, resolved, closed, cancelled, scheduled, in_progress, completed. Example: in_triage. One of: `in_triage`, `started`, `detected`, `acknowledged`, `mitigated`, `resolved`, `closed`, `cancelled`, `scheduled`, `in_progress`, `completed`.
- `summary` (`string`, optional): The summary of the incident. Example: Elevated p99 latency on the checkout API.
- `title` (`string`, optional): The title of the incident. We will autogenerate one if null. Example: Checkout API latency.
- `url` (`string`, optional): The url to the incident. Example: https://example.com/runbook.
- `user_id` (`string`, optional): User ID of the creator of the incident. Default to the user attached to the Api Key. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{}`

### `rootly_create_incident_action_item`

Create Incident Action Item · Write

Create an incident action item.
Returns the incident_action_item record with id, type and attributes (summary, description, kind, assigned_to, assigned_to_group_ids, priority).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `summary` (`string`, required): The summary of the action item. Example: Elevated p99 latency on the checkout API.
- `assigned_to_group_ids` (`array`, optional): IDs of groups you wish to assign this action item. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `assigned_to_user_id` (`integer`, optional): ID of user you wish to assign this action item. Example: 12345.
- `description` (`string`, optional): The description of the action item. Example: Elevated p99 latency on the checkout API.
- `due_date` (`string`, optional): The due date of the action item. Example: 2025-01-31.
- `form_field_selections` (`array`, optional): Custom field values to set on the action item. Ignored unless custom fields for action items are enabled for the organization. Example: [{"key": "value"}]
- `jira_issue_id` (`string`, optional): The Jira issue ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `jira_issue_key` (`string`, optional): The Jira issue key. Example: OPS-123.
- `jira_issue_url` (`string`, optional): The Jira issue URL. Example: https://example.com/runbook.
- `kind` (`string`, optional): The kind of the action item. One of: task, follow_up. Example: task. One of: `task`, `follow_up`.
- `priority` (`string`, optional): The priority of the action item. One of: high, medium, low. Example: high. One of: `high`, `medium`, `low`.
- `status` (`string`, optional): The status of the action item. One of: open, in_progress, cancelled, done. Example: open. One of: `open`, `in_progress`, `cancelled`, `done`.

Example input: `{"incident_id":"<incident_id>","summary":"<summary>"}`

### `rootly_create_incident_event`

Create Incident Event · Write

Create an incident event.
Returns the incident_event record with id, type and attributes (event, visibility, occurred_at, created_at, updated_at).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `event` (`string`, required): The summary of the incident event. Example: Example event.
- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `visibility` (`string`, optional): The visibility of the incident action item. One of: internal, external. Example: internal. One of: `internal`, `external`.

Example input: `{"event":"<event>","incident_id":"<incident_id>"}`

### `rootly_create_incident_status_page_event`

Create Incident Status Page Event · Write

Create an incident status page event.
Returns the incident_status_page_event record with id, type and attributes (event, status_page_id, status, notify_subscribers, should_tweet, status_page_components).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `event` (`string`, required): The summary of the incident event. Example: Example event.
- `incident_id` (`string`, required): The id (UUID) of the parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `notify_subscribers` (`boolean`, optional): Notify all status pages subscribers. Example: true.
- `should_tweet` (`boolean`, optional): For Statuspage.io integrated pages auto publishes a tweet for your update. Example: true.
- `started_at` (`string`, optional): When the event started. Defaults to the time of creation. Example: 2025-01-15T14:30:00Z.
- `status` (`string`, optional): The status of the incident event. Defaults to investigating, which is only valid for incidents; scheduled maintenances must set a maintenance status (e.g. scheduled, in_progress, completed) or the request is rejected with a 422. One of: investigating, identified, monitoring, resolved, scheduled, in_progress, completed. Example: investigating. One of: `investigating`, `identified`, `monitoring`, `resolved`, `scheduled`, `in_progress`, `completed`.
- `status_page_components` (`array`, optional): Affected status page components and their statuses. This field is in Early Access and is not generally available; contact Rootly Support to request access. Ignored for terminal event statuses (resolved, completed), which clear component impact. A status is required per component except for scheduled maintenance incidents. Example: [{"key": "value"}]
- `status_page_id` (`string`, optional): Unique ID of the status page you wish to post the event to. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"event":"<event>","incident_id":"<incident_id>"}`

### `rootly_create_pulse`

Create Pulse · Write

Create a pulse.
Returns the pulse record with id, type and attributes (source, summary, services, environments, external_url, labels).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `summary` (`string`, required): The summary of the pulse. Example: Elevated p99 latency on the checkout API.
- `data` (`object`, optional): Additional data. Provide as a JSON object. Example: {"key": "value"}
- `ended_at` (`string`, optional): Pulse end datetime. Example: 2025-01-15T14:30:00Z.
- `environment_ids` (`array`, optional): The Environment IDs to attach to the pulse. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `external_url` (`string`, optional): The external url of the pulse. Example: https://example.com/runbook.
- `labels` (`array`, optional): The labels value. Example: [{"key": "value"}]
- `refs` (`array`, optional): The refs value. Example: [{"key": "value"}]
- `service_ids` (`array`, optional): The Service IDs to attach to the pulse. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `source` (`string`, optional): The source of the pulse (eg: k8s). Example: Example source.
- `started_at` (`string`, optional): Pulse start datetime. Example: 2025-01-15T14:30:00Z.

Example input: `{"summary":"<summary>"}`

### `rootly_create_schedule_override_shift`

Create Schedule Override Shift · Write

create an override shift.
Returns the shift record with id, type and attributes (schedule_id, rotation_id, starts_at, ends_at, is_override, created_at).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `ends_at` (`string`, required): End datetime of override shift. Example: 2025-01-15T14:30:00Z.
- `schedule_id` (`string`, required): The id (UUID) of the parent schedule. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `starts_at` (`string`, required): Start datetime of override shift. Example: 2025-01-15T14:30:00Z.
- `user_id` (`integer`, required): Override shift user. Example: 12345.

Example input: `{"ends_at":"<ends_at>","schedule_id":"<schedule_id>","starts_at":"<starts_at>","user_id":12345}`

### `rootly_create_service`

Create Service · Write

Create a service.
Returns the service record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the service. Example: Checkout API latency.
- `alert_broadcast_channel` (`object`, optional): Slack channel to broadcast alerts to. Provide as a JSON object. Example: {"key": "value"}
- `alert_broadcast_enabled` (`boolean`, optional): Enable alerts to be broadcasted to a specific channel. Example: true.
- `alert_urgency_id` (`string`, optional): The alert urgency id of the service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `alerts_email_enabled` (`boolean`, optional): Enable alerts through email. Example: oncall@example.com.
- `backstage_id` (`string`, optional): The Backstage entity id associated to this service. eg: :namespace/:kind/:entity_name. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `color` (`string`, optional): The hex color of the service. Example: #6D55BD.
- `cortex_id` (`string`, optional): The Cortex group id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `description` (`string`, optional): The description of the service. Example: Elevated p99 latency on the checkout API.
- `environment_ids` (`array`, optional): Environments associated with this service. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `escalation_policy_id` (`string`, optional): The escalation policy id of the service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `external_id` (`string`, optional): The external id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `github_repository_branch` (`string`, optional): The GitHub repository branch associated to this service. eg: main. Example: Example github repository branch.
- `github_repository_name` (`string`, optional): The GitHub repository name associated to this service. eg: rootlyhq/my-service. Example: Example github repository name.
- `gitlab_repository_branch` (`string`, optional): The GitLab repository branch associated to this service. eg: main. Example: Example gitlab repository branch.
- `gitlab_repository_name` (`string`, optional): The GitLab repository name associated to this service. eg: rootlyhq/my-service. Example: Example gitlab repository name.
- `incident_broadcast_channel` (`object`, optional): Slack channel to broadcast incidents to. Provide as a JSON object. Example: {"key": "value"}
- `incident_broadcast_enabled` (`boolean`, optional): Enable incidents to be broadcasted to a specific channel. Example: true.
- `kubernetes_deployment_name` (`string`, optional): The Kubernetes deployment name associated to this service. eg: namespace/deployment-name. Example: Example kubernetes deployment name.
- `notify_emails` (`array`, optional): Emails to attach to the service. Example: ["example"]
- `opsgenie_id` (`string`, optional): The Opsgenie service id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `opsgenie_team_id` (`string`, optional): The Opsgenie team id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `owner_group_ids` (`array`, optional): Owner Teams associated with this service. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `owner_user_ids` (`array`, optional): Owner Users associated with this service. Example: [{"key": "value"}]
- `pagerduty_id` (`string`, optional): The PagerDuty service id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `position` (`integer`, optional): Position of the service. Example: 10.
- `properties` (`array`, optional): Array of property values for this service. Example: [{"key": "value"}]
- `public_description` (`string`, optional): The status page description of the service. Example: Elevated p99 latency on the checkout API.
- `service_ids` (`array`, optional): Services dependent on this service. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `service_now_ci_sys_id` (`string`, optional): The Service Now CI sys id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `show_uptime` (`boolean`, optional): Show uptime. Example: 2025-01-15T14:30:00Z.
- `show_uptime_last_days` (`integer`, optional): Show uptime over x days. Example: 2025-01-15T14:30:00Z.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this service. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this service. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.

Example input: `{"name":"<name>"}`

### `rootly_create_severity`

Create Severity · Write

Create a severity.
Returns the severitie record with id, type and attributes (name, slug, description, severity, color, position).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the severity. Example: Checkout API latency.
- `color` (`string`, optional): The hex color of the severity. Example: #6D55BD.
- `description` (`string`, optional): The description of the severity. Example: Elevated p99 latency on the checkout API.
- `notify_emails` (`array`, optional): Emails to attach to the severity. Example: ["example"]
- `position` (`integer`, optional): Position of the severity. Example: 10.
- `severity` (`string`, optional): The severity of the severity. One of: critical, high, medium, low. Example: critical. One of: `critical`, `high`, `medium`, `low`.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this severity. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this severity. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.

Example input: `{"name":"<name>"}`

### `rootly_create_status_page_announcement`

Create Status Page Announcement · Write

Create a status page announcement.
Returns the status_page_announcement record with id, type and attributes (status_page_id, title, body, user_id, published_at, created_at).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body` (`string`, required): Body of the announcement. Example: Example body.
- `status_page_id` (`string`, required): The id (UUID) of the parent status page. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `title` (`string`, required): Title of the announcement. Example: Checkout API latency.
- `notify_subscribers` (`boolean`, optional): Controls if status page subscribers should be notified. Defaults to true. Example: true.

Example input: `{"body":"<body>","status_page_id":"<status_page_id>","title":"<title>"}`

### `rootly_create_team`

Create Team · Write

Create a team.
Returns the group record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it to add a new record; use the matching update tool to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The name of the team. Example: Checkout API latency.
- `admin_ids` (`array`, optional): The user ids of the admins of this team. These users must also be present in user_ids attribute. Example: [{"key": "value"}]
- `alert_broadcast_channel` (`object`, optional): Slack channel to broadcast alerts to. Provide as a JSON object. Example: {"key": "value"}
- `alert_broadcast_enabled` (`boolean`, optional): Enable alerts to be broadcasted to a specific channel. Example: true.
- `alert_urgency_id` (`string`, optional): The alert urgency id of the team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `alerts_email_enabled` (`boolean`, optional): Enable alerts through email. Example: oncall@example.com.
- `auto_add_members_scope` (`string`, optional): Visibility-scoped auto-add behavior. Only present when the `enable_scoped_incident_channel_auto_add` feature flag is on for the organization. When set, it overrides `auto_add_members_when_attached`. One of: off, public_only, public_and_test, all. Example: off. One of: `off`, `public_only`, `public_and_test`, `all`.
- `auto_add_members_when_attached` (`boolean`, optional): Auto add members to incident channel when team is attached. Example: true.
- `backstage_id` (`string`, optional): The Backstage entity id associated to this team. eg: :namespace/:kind/:entity_name. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `color` (`string`, optional): The hex color of the team. Example: #6D55BD.
- `cortex_id` (`string`, optional): The Cortex group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `description` (`string`, optional): The description of the team. Example: Elevated p99 latency on the checkout API.
- `external_id` (`string`, optional): The external id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `incident_broadcast_channel` (`object`, optional): Slack channel to broadcast incidents to. Provide as a JSON object. Example: {"key": "value"}
- `incident_broadcast_enabled` (`boolean`, optional): Enable incidents to be broadcasted to a specific channel. Example: true.
- `notify_emails` (`array`, optional): Emails to attach to the team. Example: ["example"]
- `opsgenie_id` (`string`, optional): The Opsgenie group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `opsgenie_team_id` (`string`, optional): The Opsgenie team id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `pagerduty_id` (`string`, optional): The PagerDuty group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `pagerduty_service_id` (`string`, optional): The PagerDuty service id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `pagertree_id` (`string`, optional): The PagerTree group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `position` (`integer`, optional): Position of the team. Example: 10.
- `properties` (`array`, optional): Array of property values for this team. Example: [{"key": "value"}]
- `public_description` (`string`, optional): The status page description of the team. Example: Elevated p99 latency on the checkout API.
- `schedule_override_policy` (`string`, optional): Who can create and update overrides for schedules owned by this team: `everyone` in the organization, only team `members`, or only team `admins`. Users still need override permission from their on-call role. Only available when the team-level schedule override policy feature is enabled for the organization. Requests that set it while that feature is disabled are rejected. One of: everyone, members, admins. Example: everyone. One of: `everyone`, `members`, `admins`.
- `scim_group_external_id` (`string`, optional): Link by the SCIM group's externalId from your identity provider instead of scim_group_id. Write-only. Rejected when it names a different SCIM group than scim_group_id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `scim_group_id` (`string`, optional): The SCIM group id linked to this team. Membership syncs from the SCIM group while the team keeps its own name. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `service_now_ci_sys_id` (`string`, optional): The Service Now CI sys id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this team. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this team. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.
- `user_ids` (`array`, optional): The user ids of the members of this team. Example: [{"key": "value"}]
- `victor_ops_id` (`string`, optional): The VictorOps group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"name":"<name>"}`

### `rootly_escalate_alert`

Escalate Alert · Write

Escalate an alert.
Returns the alert record with id, type and attributes (short_id, noise, source, status, summary, description).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `actor` (`object`, optional): The user to record as performing this action. Only available when actor attribution is enabled for the organization; otherwise it is ignored. Only supported with Global and Team API keys; with a Team API key the user must belong to one of the key's teams. When omitted or null, the action is attributed to the API key. Otherwise provide either `email` or `user_id`, not both. Provide as a JSON object. Example: {"key": "value"}
- `escalation_policy_id` (`string`, optional): The ID of the escalation policy to escalate to. If omitted, uses the alert's current escalation policy from metadata. Required for resolved alerts whose metadata may have been cleared. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `escalation_policy_level` (`integer`, optional): The escalation policy level to escalate to. If omitted, defaults to the next level (same EP) or level 1 (different EP). Example: 10.

Example input: `{"id":"<id>"}`

### `rootly_mitigate_incident`

Mitigate Incident · Write

Mitigate an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `mitigation_message` (`string`, optional): How was the incident mitigated?. Example: Elevated p99 latency on the checkout API.

Example input: `{"id":"<id>"}`

### `rootly_move_incident_to_triage`

Move Incident To Triage · Write

Triage an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_resolve_alert`

Resolve Alert · Write

Resolve an alert.
Returns the alert record with id, type and attributes (short_id, noise, source, status, summary, description).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `actor` (`object`, optional): The user to record as performing this action. Only available when actor attribution is enabled for the organization; otherwise it is ignored. Only supported with Global and Team API keys; with a Team API key the user must belong to one of the key's teams. When omitted or null, the action is attributed to the API key. Otherwise provide either `email` or `user_id`, not both. Provide as a JSON object. Example: {"key": "value"}
- `resolution_message` (`string`, optional): How was the alert resolved?. Example: Elevated p99 latency on the checkout API.
- `resolve_related_incidents` (`boolean`, optional): Resolve all associated incidents. Example: true.

Example input: `{"id":"<id>"}`

### `rootly_resolve_incident`

Resolve Incident · Write

Resolve an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `resolution_message` (`string`, optional): How was the incident resolved?. Example: Elevated p99 latency on the checkout API.

Example input: `{"id":"<id>"}`

### `rootly_restart_incident`

Restart Incident · Write

Restart an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_snooze_alert`

Snooze Alert · Write

Snooze an alert.
Returns the alert record with id, type and attributes (short_id, noise, source, status, summary, description).
Use it to apply this state change to an existing record by id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `delay_minutes` (`integer`, required): Number of minutes to snooze the alert for. Example: 30.
- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `actor` (`object`, optional): The user to record as performing this action. Only available when actor attribution is enabled for the organization; otherwise it is ignored. Only supported with Global and Team API keys; with a Team API key the user must belong to one of the key's teams. When omitted or null, the action is attributed to the API key. Otherwise provide either `email` or `user_id`, not both. Provide as a JSON object. Example: {"key": "value"}

Example input: `{"delay_minutes":30,"id":"<id>"}`

### `rootly_update_action_item`

Update Action Item · Write

Update an incident action item.
Returns the incident_action_item record with id, type and attributes (summary, description, kind, assigned_to, assigned_to_group_ids, priority).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `assigned_to_group_ids` (`array`, optional): IDs of groups you wish to assign this action item. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `assigned_to_user_id` (`integer`, optional): ID of user you wish to assign this action item. Example: 12345.
- `description` (`string`, optional): The description of the action item. Example: Elevated p99 latency on the checkout API.
- `due_date` (`string`, optional): The due date of the action item. Example: 2025-01-31.
- `form_field_selections` (`array`, optional): Custom field values to set on the action item. Ignored unless custom fields for action items are enabled for the organization. Example: [{"key": "value"}]
- `jira_issue_id` (`string`, optional): The Jira issue ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `jira_issue_key` (`string`, optional): The Jira issue key. Example: OPS-123.
- `jira_issue_url` (`string`, optional): The Jira issue URL. Example: https://example.com/runbook.
- `kind` (`string`, optional): The kind of the action item. One of: task, follow_up. Example: task. One of: `task`, `follow_up`.
- `priority` (`string`, optional): The priority of the action item. One of: high, medium, low. Example: high. One of: `high`, `medium`, `low`.
- `status` (`string`, optional): The status of the action item. One of: open, in_progress, cancelled, done. Example: open. One of: `open`, `in_progress`, `cancelled`, `done`.
- `summary` (`string`, optional): The summary of the action item. Example: Elevated p99 latency on the checkout API.

Example input: `{"id":"<id>"}`

### `rootly_update_alert`

Update Alert · Write

Update alert.
Returns the alert record with id, type and attributes (short_id, noise, source, status, summary, description).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `actor` (`object`, optional): The user to record as performing this action. Only available when actor attribution is enabled for the organization; otherwise it is ignored. Only supported with Global and Team API keys; with a Team API key the user must belong to one of the key's teams. When omitted or null, the action is attributed to the API key. Otherwise provide either `email` or `user_id`, not both. Provide as a JSON object. Example: {"key": "value"}
- `alert_field_values_attributes` (`array`, optional): Custom alert field values to create with the alert. Example: [{"key": "value"}]
- `alert_urgency_id` (`string`, optional): The ID of the alert urgency. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `data` (`object`, optional): Additional data. Provide as a JSON object. Example: {"key": "value"}
- `deduplication_key` (`string`, optional): Alerts sharing the same deduplication key are treated as a single alert. Example: OPS-123.
- `description` (`string`, optional): The description of the alert. Example: Elevated p99 latency on the checkout API.
- `ended_at` (`string`, optional): Alert end datetime. Example: 2025-01-15T14:30:00Z.
- `environment_ids` (`array`, optional): The Environment IDs to attach to the alert. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `external_id` (`string`, optional): External ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `external_url` (`string`, optional): External Url. Example: https://example.com/runbook.
- `functionality_ids` (`array`, optional): The Functionality IDs to attach to the alert. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `group_ids` (`array`, optional): The Group IDs to attach to the alert. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `labels` (`array`, optional): The labels value. Example: [{"key": "value"}]
- `noise` (`string`, optional): Whether the alert is marked as noise. One of: noise, not_noise. Example: noise. One of: `noise`, `not_noise`.
- `service_ids` (`array`, optional): The Service IDs to attach to the alert. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `source` (`string`, optional): Deprecated. Accepted for backwards compatibility; new clients should omit. Defaults to `api`. Example: Example source.
- `started_at` (`string`, optional): Alert start datetime. Example: 2025-01-15T14:30:00Z.
- `summary` (`string`, optional): The summary of the alert. Example: Elevated p99 latency on the checkout API.

Example input: `{"id":"<id>"}`

### `rootly_update_environment`

Update Environment · Write

Update an environment.
Returns the environment record with id, type and attributes (name, slug, managed_by, external_id, description, public_description).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `color` (`string`, optional): The hex color of the environment. Example: #6D55BD.
- `description` (`string`, optional): The description of the environment. Example: Elevated p99 latency on the checkout API.
- `external_id` (`string`, optional): The external id associated to this environment. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `name` (`string`, optional): The name of the environment. Example: Checkout API latency.
- `notify_emails` (`array`, optional): Emails to attach to the environment. Example: ["example"]
- `position` (`integer`, optional): Position of the environment. Example: 10.
- `properties` (`array`, optional): Array of property values for this environment. Example: [{"key": "value"}]
- `public_description` (`string`, optional): The status page description of the environment. Example: Elevated p99 latency on the checkout API.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this environment. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this environment. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.

Example input: `{"id":"<id>"}`

### `rootly_update_functionality`

Update Functionality · Write

Update a functionality.
Returns the functionalitie record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `backstage_id` (`string`, optional): The Backstage entity id associated to this functionality. eg: :namespace/:kind/:entity_name. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `color` (`string`, optional): The hex color of the functionality. Example: #6D55BD.
- `cortex_id` (`string`, optional): The Cortex group id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `description` (`string`, optional): The description of the functionality. Example: Elevated p99 latency on the checkout API.
- `environment_ids` (`array`, optional): Environments associated with this functionality. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `escalation_policy_id` (`string`, optional): The escalation policy id of the functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `external_id` (`string`, optional): The external id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `name` (`string`, optional): The name of the functionality. Example: Checkout API latency.
- `notify_emails` (`array`, optional): Emails to attach to the functionality. Example: ["example"]
- `opsgenie_id` (`string`, optional): The Opsgenie service id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `opsgenie_team_id` (`string`, optional): The Opsgenie team id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `owner_group_ids` (`array`, optional): Owner Teams associated with this functionality. Empty array removes all; omitting or null leaves unchanged. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `owner_user_ids` (`array`, optional): Owner Users associated with this functionality. Empty array removes all; omitting or null leaves unchanged. Example: [{"key": "value"}]
- `pagerduty_id` (`string`, optional): The PagerDuty service id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `position` (`integer`, optional): Position of the functionality. Example: 10.
- `properties` (`array`, optional): Array of property values for this functionality. Example: [{"key": "value"}]
- `public_description` (`string`, optional): The status page description of the functionality. Example: Elevated p99 latency on the checkout API.
- `service_ids` (`array`, optional): Services associated with this functionality. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `service_now_ci_sys_id` (`string`, optional): The Service Now CI sys id associated to this functionality. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this functionality. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this functionality. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.

Example input: `{"id":"<id>"}`

### `rootly_update_incident`

Update Incident · Write

Update an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `acknowledged_at` (`string`, optional): Date of acknowledgment. Example: 2025-01-15T14:30:00Z.
- `alert_ids` (`array`, optional): The Alert IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `cancellation_message` (`string`, optional): Why was the incident cancelled?. Example: Elevated p99 latency on the checkout API.
- `cancelled_at` (`string`, optional): Date of cancellation. Example: 2025-01-15T14:30:00Z.
- `cause_ids` (`array`, optional): The Cause IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `closed_at` (`string`, optional): Date of closure. Example: 2025-01-15T14:30:00Z.
- `detected_at` (`string`, optional): Date of detection. Example: 2025-01-15T14:30:00Z.
- `duplicate_incident_id` (`string`, optional): ID of duplicated incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `environment_ids` (`array`, optional): The Environment IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `functionality_ids` (`array`, optional): The Functionality IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `google_drive_parent_id` (`string`, optional): Google Drive parent folder ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `google_drive_url` (`string`, optional): Google Drive URL. Example: https://example.com/runbook.
- `group_ids` (`array`, optional): The Team IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `in_triage_at` (`string`, optional): Date of triage. Example: 2025-01-15T14:30:00Z.
- `incident_type_ids` (`array`, optional): The Incident Type IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `jira_issue_id` (`string`, optional): Jira issue ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `jira_issue_key` (`string`, optional): Jira issue key. Example: OPS-123.
- `jira_issue_url` (`string`, optional): Jira issue URL. Example: https://example.com/runbook.
- `kind` (`string`, optional): The kind of the incident. One of: test, test_sub, example, example_sub, normal, normal_sub, backfilled, scheduled, scheduled_sub. Example: test. One of: `test`, `test_sub`, `example`, `example_sub`, `normal`, `normal_sub`, `backfilled`, `scheduled`, `scheduled_sub`.
- `labels` (`object`, optional): Labels to attach to the incidents. eg: {"platform":"osx", "version": "1.29"}. Provide as a JSON object. Example: {"key": "value"}
- `linear_issue_id` (`string`, optional): Linear issue ID. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `linear_issue_key` (`string`, optional): Linear issue key. Example: OPS-123.
- `linear_issue_url` (`string`, optional): Linear issue URL. Example: https://example.com/runbook.
- `mitigated_at` (`string`, optional): Date of mitigation. Example: 2025-01-15T14:30:00Z.
- `mitigation_message` (`string`, optional): How was the incident mitigated?. Example: Elevated p99 latency on the checkout API.
- `muted_service_ids` (`array`, optional): The Service IDs to mute alerts for during maintenance. Alerts for these services will still be triggered and attached to the incident, but won't page responders. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `parent_incident_id` (`string`, optional): ID of parent incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `private` (`boolean`, optional): Convert the incident as private. Once an incident is updated as private it cannot be undone. Example: true.
- `public_title` (`string`, optional): The public title of the incident. Example: Checkout API latency.
- `resolution_message` (`string`, optional): How was the incident resolved?. Example: Elevated p99 latency on the checkout API.
- `resolved_at` (`string`, optional): Date of resolution. Example: 2025-01-15T14:30:00Z.
- `scheduled_for` (`string`, optional): Date of when the maintenance begins. Example: Example scheduled for.
- `scheduled_until` (`string`, optional): Date of when the maintenance ends. Example: Example scheduled until.
- `service_ids` (`array`, optional): The Service IDs to attach to the incident. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `severity_id` (`string`, optional): The Severity ID to attach to the incident. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `slack_channel_archived` (`boolean`, optional): Whether the Slack channel is archived. Example: true.
- `slack_channel_id` (`string`, optional): Slack channel id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `slack_channel_name` (`string`, optional): Slack channel name. Example: Example slack channel name.
- `slack_channel_url` (`string`, optional): Slack channel url. Example: https://example.com/runbook.
- `started_at` (`string`, optional): Date of start. Example: 2025-01-15T14:30:00Z.
- `status` (`string`, optional): The status of the incident. One of: in_triage, started, detected, acknowledged, mitigated, resolved, closed, cancelled, scheduled, in_progress, completed. Example: in_triage. One of: `in_triage`, `started`, `detected`, `acknowledged`, `mitigated`, `resolved`, `closed`, `cancelled`, `scheduled`, `in_progress`, `completed`.
- `summary` (`string`, optional): The summary of the incident. Example: Elevated p99 latency on the checkout API.
- `title` (`string`, optional): The title of the incident. Example: Checkout API latency.

Example input: `{"id":"<id>"}`

### `rootly_update_post_mortem`

Update Post Mortem · Write

Update an incident retrospective.
Returns the incident_post_mortem record with id, type and attributes (title, content, status, started_at, mitigated_at, resolved_at).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `cause_ids` (`array`, optional): The Cause IDs to attach to the incident retrospective. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `content` (`string`, optional): The content (body) of the incident retrospective, as HTML. Rejected with a 409 once the retrospective has been opened in the collaborative editor. Example: Elevated p99 latency on the checkout API.
- `mitigated_at` (`string`, optional): Date of mitigation. Example: 2025-01-15T14:30:00Z.
- `resolved_at` (`string`, optional): Date of resolution. Example: 2025-01-15T14:30:00Z.
- `show_action_items` (`boolean`, optional): Show action items (follow-ups) in the incident retrospective. Example: true.
- `show_alerts_attached` (`boolean`, optional): Show alerts attached to the incident. Example: true.
- `show_functionalities_impacted` (`boolean`, optional): Show services impacted of the incident retrospective. Example: true.
- `show_groups_impacted` (`boolean`, optional): Show groups impacted of the incident retrospective. Example: true.
- `show_services_impacted` (`boolean`, optional): Show functionalities impacted of the incident retrospective. Example: true.
- `show_timeline` (`boolean`, optional): Show events timeline of the incident retrospective. Example: 2025-01-15T14:30:00Z.
- `show_timeline_action_items` (`boolean`, optional): Show action items in the timeline of the incident retrospective. Example: 2025-01-15T14:30:00Z.
- `show_timeline_genius` (`boolean`, optional): Show workflow events in the timeline of the incident retrospective. Example: 2025-01-15T14:30:00Z.
- `show_timeline_tasks` (`boolean`, optional): Show tasks in the timeline of the incident retrospective. Example: 2025-01-15T14:30:00Z.
- `show_timeline_trail` (`boolean`, optional): Show trail events in the timeline of the incident retrospective. Example: 2025-01-15T14:30:00Z.
- `started_at` (`string`, optional): Date of started at. Example: 2025-01-15T14:30:00Z.
- `status` (`string`, optional): The status of the incident retrospective. One of: draft, published. Example: draft. One of: `draft`, `published`.
- `title` (`string`, optional): The title of the incident retrospective. Example: Checkout API latency.

Example input: `{"id":"<id>"}`

### `rootly_update_service`

Update Service · Write

Update a service.
Returns the service record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `alert_broadcast_channel` (`object`, optional): Slack channel to broadcast alerts to. Provide as a JSON object. Example: {"key": "value"}
- `alert_broadcast_enabled` (`boolean`, optional): Enable alerts to be broadcasted to a specific channel. Example: true.
- `alert_urgency_id` (`string`, optional): The alert urgency id of the service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `alerts_email_enabled` (`boolean`, optional): Enable alerts through email. Example: oncall@example.com.
- `backstage_id` (`string`, optional): The Backstage entity id associated to this service. eg: :namespace/:kind/:entity_name. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `color` (`string`, optional): The hex color of the service. Example: #6D55BD.
- `cortex_id` (`string`, optional): The Cortex group id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `description` (`string`, optional): The description of the service. Example: Elevated p99 latency on the checkout API.
- `environment_ids` (`array`, optional): Environments associated with this service. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `escalation_policy_id` (`string`, optional): The escalation policy id of the service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `external_id` (`string`, optional): The external id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `github_repository_branch` (`string`, optional): The GitHub repository branch associated to this service. eg: main. Example: Example github repository branch.
- `github_repository_name` (`string`, optional): The GitHub repository name associated to this service. eg: rootlyhq/my-service. Example: Example github repository name.
- `gitlab_repository_branch` (`string`, optional): The GitLab repository branch associated to this service. eg: main. Example: Example gitlab repository branch.
- `gitlab_repository_name` (`string`, optional): The GitLab repository name associated to this service. eg: rootlyhq/my-service. Example: Example gitlab repository name.
- `incident_broadcast_channel` (`object`, optional): Slack channel to broadcast incidents to. Provide as a JSON object. Example: {"key": "value"}
- `incident_broadcast_enabled` (`boolean`, optional): Enable incidents to be broadcasted to a specific channel. Example: true.
- `kubernetes_deployment_name` (`string`, optional): The Kubernetes deployment name associated to this service. eg: namespace/deployment-name. Example: Example kubernetes deployment name.
- `name` (`string`, optional): The name of the service. Example: Checkout API latency.
- `notify_emails` (`array`, optional): Emails to attach to the service. Example: ["example"]
- `opsgenie_id` (`string`, optional): The Opsgenie service id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `owner_group_ids` (`array`, optional): Owner Teams associated with this service. Empty array removes all; omitting or null leaves unchanged. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `owner_user_ids` (`array`, optional): Owner Users associated with this service. Empty array removes all; omitting or null leaves unchanged. Example: [{"key": "value"}]
- `pagerduty_id` (`string`, optional): The PagerDuty service id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `position` (`integer`, optional): Position of the service. Example: 10.
- `properties` (`array`, optional): Array of property values for this service. Example: [{"key": "value"}]
- `public_description` (`string`, optional): The status page description of the service. Example: Elevated p99 latency on the checkout API.
- `service_ids` (`array`, optional): Services dependent on this service. Example: ["a1b2c3d4-e5f6-4789-a012-3456789abcde"]
- `service_now_ci_sys_id` (`string`, optional): The Service Now CI sys id associated to this service. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this service. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this service. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.

Example input: `{"id":"<id>"}`

### `rootly_update_severity`

Update Severity · Write

Update a severity.
Returns the severitie record with id, type and attributes (name, slug, description, severity, color, position).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `color` (`string`, optional): The hex color of the severity. Example: #6D55BD.
- `description` (`string`, optional): The description of the severity. Example: Elevated p99 latency on the checkout API.
- `name` (`string`, optional): The name of the severity. Example: Checkout API latency.
- `notify_emails` (`array`, optional): Emails to attach to the severity. Example: ["example"]
- `position` (`integer`, optional): Position of the severity. Example: 10.
- `severity` (`string`, optional): The severity of the severity. One of: critical, high, medium, low. Example: critical. One of: `critical`, `high`, `medium`, `low`.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this severity. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this severity. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.

Example input: `{"id":"<id>"}`

### `rootly_update_status_page_event`

Update Status Page Event · Write

Update an incident status page event.
Returns the incident_status_page_event record with id, type and attributes (event, status_page_id, status, notify_subscribers, should_tweet, status_page_components).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `event` (`string`, optional): The summary of the incident event. Example: Example event.
- `notify_subscribers` (`boolean`, optional): Notify all status pages subscribers. Example: true.
- `should_tweet` (`boolean`, optional): For Statuspage.io integrated pages auto publishes a tweet for your update. Example: true.
- `started_at` (`string`, optional): When the event started. Example: 2025-01-15T14:30:00Z.
- `status` (`string`, optional): The status of the incident event. One of: investigating, identified, monitoring, resolved, scheduled, in_progress, completed. Example: investigating. One of: `investigating`, `identified`, `monitoring`, `resolved`, `scheduled`, `in_progress`, `completed`.
- `status_page_id` (`string`, optional): Unique ID of the status page you wish to post the event to. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_update_team`

Update Team · Write

Update a team.
Returns the group record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it to change an existing record by id; only the fields you supply are changed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `admin_ids` (`array`, optional): The user ids of the admins of this team. These users must also be present in user_ids attribute. Example: [{"key": "value"}]
- `alert_broadcast_channel` (`object`, optional): Slack channel to broadcast alerts to. Provide as a JSON object. Example: {"key": "value"}
- `alert_broadcast_enabled` (`boolean`, optional): Enable alerts to be broadcasted to a specific channel. Example: true.
- `alert_urgency_id` (`string`, optional): The alert urgency id of the team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `alerts_email_enabled` (`boolean`, optional): Enable alerts through email. Example: oncall@example.com.
- `auto_add_members_scope` (`string`, optional): Visibility-scoped auto-add behavior. Only present when the `enable_scoped_incident_channel_auto_add` feature flag is on for the organization. When set, it overrides `auto_add_members_when_attached`. One of: off, public_only, public_and_test, all. Example: off. One of: `off`, `public_only`, `public_and_test`, `all`.
- `auto_add_members_when_attached` (`boolean`, optional): Auto add members to incident channel when team is attached. Example: true.
- `backstage_id` (`string`, optional): The Backstage entity id associated to this team. eg: :namespace/:kind/:entity_name. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `color` (`string`, optional): The hex color of the team. Example: #6D55BD.
- `cortex_id` (`string`, optional): The Cortex group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `description` (`string`, optional): The description of the team. Example: Elevated p99 latency on the checkout API.
- `external_id` (`string`, optional): The external id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `incident_broadcast_channel` (`object`, optional): Slack channel to broadcast incidents to. Provide as a JSON object. Example: {"key": "value"}
- `incident_broadcast_enabled` (`boolean`, optional): Enable incidents to be broadcasted to a specific channel. Example: true.
- `name` (`string`, optional): The name of the team. Example: Checkout API latency.
- `notify_emails` (`array`, optional): Emails to attach to the team. Example: ["example"]
- `opsgenie_id` (`string`, optional): The Opsgenie group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `pagerduty_id` (`string`, optional): The PagerDuty group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `pagerduty_service_id` (`string`, optional): The PagerDuty service id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `pagertree_id` (`string`, optional): The PagerTree group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `position` (`integer`, optional): Position of the team. Example: 10.
- `properties` (`array`, optional): Array of property values for this team. Example: [{"key": "value"}]
- `public_description` (`string`, optional): The status page description of the team. Example: Elevated p99 latency on the checkout API.
- `schedule_override_policy` (`string`, optional): Who can create and update overrides for schedules owned by this team: `everyone` in the organization, only team `members`, or only team `admins`. Users still need override permission from their on-call role. Only available when the team-level schedule override policy feature is enabled for the organization. Requests that set it while that feature is disabled are rejected. One of: everyone, members, admins. Example: everyone. One of: `everyone`, `members`, `admins`.
- `scim_group_external_id` (`string`, optional): Link by the SCIM group's externalId from your identity provider instead of scim_group_id. Write-only. Rejected when it names a different SCIM group than scim_group_id. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `scim_group_id` (`string`, optional): The SCIM group id linked to this team. Membership syncs from the SCIM group while the team keeps its own name. Set to null to unlink. Sending the current id is a no-op; to pin a name-linked group, unlink then link. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `service_now_ci_sys_id` (`string`, optional): The Service Now CI sys id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.
- `slack_aliases` (`array`, optional): Slack Aliases associated with this team. Example: [{"key": "value"}]
- `slack_channels` (`array`, optional): Slack Channels associated with this team. Example: [{"key": "value"}]
- `slug` (`string`, optional): Deprecated. `slug` is derived from `name`; any submitted value is ignored. This property will be removed from the request schema in a future version. Example: database-primary.
- `user_ids` (`array`, optional): The user ids of the members of this team. Example: [{"key": "value"}]
- `victor_ops_id` (`string`, optional): The VictorOps group id associated to this team. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_delete_action_item`

Delete Action Item · Destructive

Delete an incident action item.
Returns the incident_action_item record with id, type and attributes (summary, description, kind, assigned_to, assigned_to_group_ids, priority).
Use it only when the record must be removed permanently; this cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_delete_incident`

Delete Incident · Destructive

Delete an incident.
Returns the incident record with id, type and attributes (sequential_id, title, kind, slug, parent_incident_id, duplicate_incident_id).
Use it only when the record must be removed permanently; this cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

### `rootly_delete_service`

Delete Service · Destructive

Delete a service.
Returns the service record with id, type and attributes (name, slug, managed_by, description, public_description, notify_emails).
Use it only when the record must be removed permanently; this cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The UUID or slug of the target record, as returned by the matching list tool. Example: a1b2c3d4-e5f6-4789-a012-3456789abcde.

Example input: `{"id":"<id>"}`

## Related

Other Monitoring connectors ([all 29](/agentkit/connectors/?category=monitoring)):

- [Microsoft Entra ID](/agentkit/connectors/microsoftentraid/): Scalekit connector, OAuth, 82 tools
- [Datadog](/agentkit/connectors/datadog/): Scalekit connector, API key, 105 tools
- [1Password](/agentkit/connectors/onepassword/): Scalekit connector, Access token, 4 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |