Skip to main content
Glama
OctopusDeploy

Octopus Deploy MCP Server

Official

Find deployment targets in an Octopus Deploy space

find_deployment_targets
Read-onlyIdempotent

Find deployment targets in a space: get a single target by ID or list all with optional filters like name, roles, health status, and environment.

Instructions

Find deployment targets (machines) in a space - can retrieve a single target by ID or list all targets

This unified tool can either:

  • Get detailed information about a specific deployment target when targetId is provided

  • List all deployment targets in a space when targetId is omitted

You can optionally filter by various parameters like name, roles, health status, etc. when listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNameYes
targetIdNoThe ID of a specific deployment target to retrieve. If omitted, lists all deployment targets.
skipNoNumber of targets to skip for pagination (only used when listing)
takeNoNumber of targets to take for pagination (only used when listing)
nameNoFilter by exact name (only used when listing)
idsNoFilter by specific target IDs (only used when listing)
partialNameNoFilter by partial name match (only used when listing)
rolesNoA list of roles / target tags to filter by (only used when listing)
isDisabledNoFilter by disabled status (only used when listing)
healthStatusesNoPossible values: Healthy, Unhealthy, Unavailable, Unknown, HasWarnings (only used when listing)
commStylesNoFilter by communication styles (only used when listing)
tenantIdsNoFilter by tenant IDs (only used when listing)
tenantTagsNoFilter by tenant tags (only used when listing)
environmentIdsNoFilter by environment IDs (only used when listing)
thumbprintNoFilter by thumbprint (only used when listing)
deploymentIdNoFilter by deployment ID (only used when listing)
shellNamesNoFilter by shell names (only used when listing)
deploymentTargetTypesNoFilter by deployment target types (only used when listing)
Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent behavior. The description adds context about the dual mode (single vs list) and filtering, but does not disclose potential pagination limits or error handling beyond what is in schema.

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

Conciseness5/5

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

The description is concise at three sentences plus bullet points, front-loading the purpose and clearly separating the two usage modes. Every sentence is informative without redundancy.

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 18 parameters and no output schema, the description adequately explains the two modes and optional filters. It lacks details about return structure or pagination behavior, but the schema covers parameter descriptions well, and annotations provide safety context.

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 94%, so the schema does most of the work. The description minimally adds 'filter by various parameters' but does not elaborate on parameter usage or provide examples beyond what the schema descriptions already offer.

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 title and description clearly state the tool finds deployment targets in Octopus Deploy. It specifies two modes: retrieve by ID or list all, which distinguishes its functionality from sibling tools like find_accounts or find_certificates.

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 description explicitly explains when to use each mode (with targetId vs without) and mentions filtering options for listing. However, it does not mention when not to use this tool or suggest alternatives among siblings.

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