Skip to main content
Glama
Cutover MCP

Cutover MCP

Official
by gocutover

List Runbooks

list_runbooks

Lists all runbooks in a specified workspace, with filters for archived status, folder, template status, and source template, so you can find the exact runbooks you need.

Instructions

List all runbooks in a specific workspace.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_runbooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
archivedNoFilter by archived status. Pass false to exclude archived runbooks, true to show only archived.
folder_idNoFilter to only runbooks in this folder ID.
is_templateNoFilter by template status. Pass false to exclude templates, true to show only templates.
extra_paramsNoAdditional query parameters to pass to the API (e.g. {"stage": "active"}).
workspace_idYesThe unique identifier for the workspace.
source_runbook_idNoFilter to only runbooks created from this template ID.

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

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. It does not say whether results are paginated (despite 'all'), what the default archived/template inclusion behavior is, whether workspace permissions are required, or how the response is shaped.

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 front-loaded sentence with no wasted words. It is efficient, though the terseness borders on under-specification given the six available parameters.

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?

The description is complete enough for a straightforward list operation whose parameters are fully documented in the schema and whose return values are covered by an output schema. The main gap is the lack of any note on pagination or default filter behavior implied by 'List all'.

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 all six parameters, including archived, folder_id, is_template, and source_runbook_id filters, are documented in the schema itself. The description adds no additional meaning beyond what the schema already provides, so the baseline of 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?

States a specific verb ('List') and resource ('runbooks') scoped to a workspace, which is clear enough to distinguish from get_runbook_by_id or create_runbook. It does not explicitly name a sibling or clarify why one would list versus fetch a single 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 Guidelines2/5

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

There is no when-to-use guidance and no mention of the alternatives (get_runbook_by_id, list_runbook_types) or when this listing should be preferred. It also never hints that filtering options exist, leaving the agent to infer usage entirely.

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