Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Get Ai Automation Run

get_ai_automation_run
Read-only

Retrieve a single AI automation run by ID to inspect its status, timing, trigger, linked incident, and agent output in read-only mode.

Instructions

Get one AI automation run by id: its status, timing, what triggered it, the linked incident if any, and the agent's output. Read-only.

Incident-linked runs are visible only when the caller's role permits access. OAuth tokens also need the ir.incidents:read scope; API keys use the key's role. Requires OAuth scope ai.automations:write.

Tool call template

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

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired. ID of the automation run (fills `{id}` in /v1/ai/automation_runs/{id}). Pass it as `id` -- this tool has no `automation_run_id` argument.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description goes beyond them by disclosing role-gated visibility of incident-linked runs and the required OAuth scopes. The trailing 'Requires OAuth scope `ai.automations:write`' is slightly confusing for a read-only tool but reflects a permission requirement, not a behavioral contradiction with the annotations.

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

Conciseness4/5

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

The return contents and the read-only nature are front-loaded in one dense sentence, followed by two short permission sentences. Minor waste in the redundant overlap between the role-based visibility sentence and the scope sentence, and the scope sentence could clarify why a write scope is needed for a read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup with an output schema present, the description covers the remaining gaps an agent actually needs: response shape summary, read-only semantics, and both role- and scope-based access constraints. Return-value detail is correctly left to the output schema.

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

Parameters3/5

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

Schema coverage is 100% and the schema itself already explains that the UUID fills `{id}` and is not `automation_run_id`. The description adds only the phrase 'by id', so the schema does essentially all the parameter work; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Get one AI automation run by id') and enumerates what the response contains: status, timing, trigger, linked incident, and agent output. 'One ... run' plus 'by id' distinguishes it from the list_ai_automation_runs and get_ai_automation siblings without the agent needing to open either schema.

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

Usage Guidelines3/5

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

Usage is implied by 'by id' and 'Read-only', and the access conditions (role-based incident visibility, `ir.incidents:read` scope for OAuth, key role for API keys) tell the caller whether they can use it. However, it never states when to reach for this versus list_ai_automation_runs or get_ai_automation, so routing remains inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools