Skip to main content
Glama
OctopusDeploy

Octopus Deploy MCP Server

Official

Find runbooks in a project

find_runbooks
Read-onlyIdempotent

List or fetch runbooks in an Octopus Deploy project by ID, slug, or git ref, with filtering options for partial name and pagination.

Instructions

Find runbooks in an Octopus Deploy project.

Two project kinds are supported:

  • DB-backed projects: address runbooks by 'runbookId' (e.g. 'Runbooks-123'). The summary includes 'publishedRunbookSnapshotId', which run_runbook uses by default.

  • Config-as-Code (CaC) projects: pass 'gitRef' (branch name like 'main', tag, or commit SHA). Address a single runbook by 'runbookSlug'. The summary includes 'gitRef' instead of 'publishedRunbookSnapshotId'; run_runbook needs the same gitRef.

Modes:

  • runbookId → fetch a single DB runbook.

  • runbookSlug + gitRef → fetch a single CaC runbook.

  • gitRef alone → list CaC runbooks at that ref.

  • neither → list DB runbooks in the project (optionally filtered by partialName).

Each summary includes multiTenancyMode and environmentScope so callers can determine which environments and tenants are valid targets before invoking run_runbook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNameYesSpace name.
projectNameYesProject name. Runbooks are scoped to a project, so this is required for both single fetch and listing.
runbookIdNoFetch a single DB-backed runbook by ID (e.g. 'Runbooks-123'). Mutually exclusive with partialName/skip/take and with gitRef/runbookSlug.
runbookSlugNoConfig-as-Code only. Fetch a single CaC runbook by slug at the given gitRef. Requires gitRef.
gitRefNoFor Config-as-Code projects only. A branch name (e.g. 'main'), tag, or commit SHA. Use get_branches to list available branches.
partialNameNoFilter listing by partial runbook name (case-insensitive).
skipNoPagination offset.
takeNoPagination page size.
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable context about the summary fields (multiTenancyMode, environmentScope) and how they support pre-execution validation, which annotations alone do not convey.

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?

Well-organized with clear sections (overview, project kinds, modes, summary). It is slightly lengthy but each sentence adds value. The structure aids quick comprehension.

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?

Given the complexity (8 parameters, multiple modes, no output schema), the description covers all necessary aspects: mode selection, parameter relationships, and summary output details. It enables correct invocation without additional context.

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

Parameters4/5

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

Input schema provides 100% coverage with descriptions for all 8 parameters. The description enriches this by explaining the logical groupings and mutual exclusions (e.g., runbookId vs gitRef/runbookSlug), and clarifies how parameters interact in different modes.

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 clearly states it finds runbooks in Octopus Deploy projects, distinguishes between DB-backed and CaC runbook modes, and differentiates from sibling tools like run_runbook. Each mode is explicitly named and scoped.

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

Usage Guidelines5/5

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

Explicitly explains when to use each mode (runbookId, runbookSlug+gitRef, gitRef alone, neither), including mutual exclusivity and required conditions. Also references get_branches for branch listing and run_runbook for execution, providing clear alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OctopusDeploy/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server