Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

Update Runbook Task

update_runbook_task

Modify an existing runbook task's details, dependencies, schedule, assignees, or type to keep execution plans current.

Instructions

Update an existing task in a runbook (including dependencies, description, stream, duration, etc.).

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>",
      "task_id": "<task_id>"
    },
    "name": "update_runbook_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe new name for the task.
levelNoThe task's level (default level_3).
messageNoFor an Email/SMS/Call comms task, the message body. For an agentic task, the initial prompt the AI agent receives when the task starts: when the user asks to set, change or rewrite an agentic task's prompt or instructions, update this field.
task_idYesThe ID of the task to update.
durationNoPlanned duration in seconds.
assigneesNoList of assignees to add to the task. Only users and teams that are already participants on the runbook can be assigned; non-participants are silently ignored by the API. By default these are added without removing existing assignees; set delete_excluded_assignees=True to replace the full list instead.
end_fixedNoISO 8601 timestamp fixing the task's end time.
stream_idNoThe ID of the stream to assign the task to (can be a substream).
auto_startNoWhether the task should start automatically once its predecessors complete.
recipientsNoList of recipients for a comms task (Email/SMS/Call).
runbook_idYesThe ID of the runbook containing the task.
task_linksNoReplaces the task's links to other resources. Use ``link_type="runbook"`` to link a task to a template runbook — the target must be a template runbook and must have ≥1 task. Use ``link_type="snippet"`` to attach one or more snippets. Pass an empty list to clear all links.
auto_finishNoWhether the task should complete automatically once started.
descriptionNoThe new description for the task.
start_fixedNoISO 8601 timestamp fixing the task's start time.
predecessorsNoA list of task IDs that are predecessors to this task.
task_type_idNoTask type ID from ``list_task_types`` (integration-backed and agentic types included) to change what kind of task this is.
custom_field_valuesNoCustom field values to update. Identify each field by custom_field_id, using the id returned by list_custom_fields with scope="task": {"custom_field_id": "123", "value": ...}. A field's internal ``name`` can be used instead of the id, but its ``display_name`` cannot. For select_menu and radiobox fields, pass the option name; for checkboxes, pass a list of option names. Pass "" to clear a field. If the API reports 'Custom field "" was not found' for a valid id, the field is most likely not available for the task's type. Values in the response are listed by ``name``, with custom_field_id set to null.
delete_excluded_assigneesNoWhen False (default), adds the given assignees without removing existing ones. When True, replaces the full assignee list with only the assignees provided.

Output Schema

NameRequiredDescriptionDefault
dataYes
includedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description bears the full behavioral burden and adds little: it does not state that this is a mutation, whether omitted fields are left untouched (partial update) versus reset, whether clearing values is supported, or what side effects occur (notifications to new assignees, rescheduling when dependencies change). The schema hints at some of this, but the description itself provides none of 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?

A single compact sentence with the key concept (task, runbook, update) front-loaded and no wasted preamble. The parenthetical "etc." is slightly loose but does not bloat the definition.

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

Completeness2/5

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

For a 19-parameter mutation tool with no annotations, the description should carry more: partial-update semantics, permission requirements, and side effects on scheduling or notifications are all missing. An output schema exists so return values need not be explained, but the mutation contract itself is under-described.

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% and the schema already explains the nontrivial parameters in depth (assignee add-vs-replace, task_links replacement, custom field clearing). The description adds no parameter-level meaning beyond loosely echoing field names like dependencies, description, stream and duration, so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific verb and resource ("Update an existing task in a runbook") and enumerates several updatable facets, so the agent knows exactly what the tool mutates. It stops short of distinguishing itself from siblings such as add_task_to_runbook or complete_task, but the verb/resource pairing is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives (add_task_to_runbook for creation, complete_task or skip_task for status changes), and no prerequisites such as needing write access or the task already existing. Usage is only inferable from the word "Update".

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