Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Get Runbook Tasks

get_runbook_tasks

Fetch tasks for a specific runbook with optional filtering and sorting, or use forecast mode to return all tasks with timing and dependency data for timeline views.

Instructions

Fetch tasks for a specific runbook, with optional filtering and sorting.

This endpoint has two modes:

  • Conventional mode: supports filtering, pagination, and sorting.

  • Forecast mode (forecast=true): returns ALL tasks in a single response regardless of pagination or filters, and includes computed timing fields start_display and end_display, plus predecessor/successor graph relationships. Use for timeline or dependency views.

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": {
      "runbook_id": "<runbook_id>"
    },
    "name": "get_runbook_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order. Example: start_planned or -start_planned (descending).
levelNoFilter by task level.
stageNoFilter by task stage(s). Allowed: default, startable, in_progress, complete.
user_idNoFilter to tasks assigned to these user ID(s).
forecastNoWhen true, returns all tasks with computed forecast fields (start_display, end_display) and graph info (predecessors, successors). Overrides pagination and filters.
stream_idNoFilter to tasks in these stream ID(s).
runbook_idYesThe unique identifier for the runbook.
fields_taskNoSpecific task fields to return (maps to fields[task]). Reduces payload size. Attributes: created_at, comments_count, completion_type, custom_field_values, description, disable_notify, duration, elapsed_duration, is_late, end_actual, end_display (forecast only), end_fixed, end_planned, end_requirements, level, message, name, start_actual, start_display (forecast only), start_requirements, start_fixed, start_planned, start_ready, updated_at, stage. Relationships: predecessors, source_runbook, source_task, successors, stream, task_type.
search_termNoFilter tasks by search term matched against task name.
has_commentsNoWhen true, return only tasks that have comments.
task_type_idNoFilter to tasks of these task type ID(s).
completion_typeNoFilter by completion type. Allowed: complete_normal, complete_skipped, complete_abandoned, complete_auto.
runbook_team_idNoFilter to tasks assigned to these runbook team ID(s).
source_runbook_idNoFilter to tasks originating from these source runbook ID(s).

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYesTop-level metadata for a list response.
linksYesPagination links for a list response.
includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose important non-obvious behavior: forecast mode returns ALL tasks in a single response regardless of pagination or filters, and adds computed fields plus predecessor/successor relationships. It omits auth/permission requirements and doesn't explicitly state the operation is read-only, though 'Fetch' implies it.

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?

Front-loaded one-line purpose followed by a short two-bullet mode breakdown; every sentence is functional. Minor redundancy since the forecast override is restated from the schema's forecast parameter description.

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

Completeness4/5

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

A 14-parameter read tool with a full output schema; the description covers the key decision point (forecast vs conventional) and return-shape differences, so an agent can call it correctly. Remaining details like default page size are handled by the schema and 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 description coverage is 100%, so the schema already documents all 14 parameters including forecast's override behavior. The description adds mode-level framing of how forecast interacts with the other parameters but no parameter-specific detail beyond the schema, matching the baseline 3.

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?

States a specific verb and resource ('Fetch tasks for a specific runbook') plus the scope of optional filtering and sorting, which clearly separates it from sibling tools like add_task_to_runbook, update_runbook_task, and get_runbook_by_id.

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

Usage Guidelines4/5

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

The two-mode framing tells the agent when to use forecast mode ('Use for timeline or dependency views') versus conventional filtered/paginated mode. It stops short of naming alternative tools or stating explicit exclusions, so it is clear context rather than full routing guidance.

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