Skip to main content
Glama
OctopusDeploy

Octopus Deploy MCP Server

Official

list_releases

Read-only

Retrieve all releases within a specified Octopus Deploy space, with optional pagination controls for managing large result sets.

Instructions

List releases in a space

This tool lists all releases in a given space. The space name is required. Optionally provide skip and take parameters for pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNameYesThe space name
skipNo
takeNo

Implementation Reference

  • The handler function that creates an Octopus Deploy client, fetches releases for the given space with optional pagination, and returns formatted JSON response.
    async ({ spaceName, skip, take }) => {
      const configuration = getClientConfigurationFromEnvironment();
      const client = await Client.create(configuration);
      const releaseRepository = new ReleaseRepository(client, spaceName);
    
      const releasesResponse = await releaseRepository.list({ skip, take });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              totalResults: releasesResponse.TotalResults,
              itemsPerPage: releasesResponse.ItemsPerPage,
              numberOfPages: releasesResponse.NumberOfPages,
              lastPageNumber: releasesResponse.LastPageNumber,
              items: releasesResponse.Items.map(release => ({
                id: release.Id,
                version: release.Version,
                channelId: release.ChannelId,
                projectId: release.ProjectId,
                releaseNotes: release.ReleaseNotes,
                assembled: release.Assembled,
                ignoreChannelRules: release.IgnoreChannelRules,
                selectedPackages: release.SelectedPackages,
                selectedGitResources: release.SelectedGitResources,
                buildInformation: release.BuildInformation,
                customFields: release.CustomFields
              }))
            }),
          },
        ],
      };
    }
  • Input schema defined with Zod validators for spaceName (required string), and optional skip/take numbers for pagination.
      spaceName: z.string().describe("The space name"),
      skip: z.number().optional(),
      take: z.number().optional()
    },
  • registerListReleasesTool: Registers the tool on the MCP server with name, description, input schema, output metadata, and handler function.
    export function registerListReleasesTool(server: McpServer) {
      server.tool(
        "list_releases",
        `List releases in a space
      
      This tool lists all releases in a given space. The space name is required. Optionally provide skip and take parameters for pagination.`,
        { 
          spaceName: z.string().describe("The space name"),
          skip: z.number().optional(),
          take: z.number().optional()
        },
        {
          title: "List all releases in an Octopus Deploy space",
          readOnlyHint: true,
        },
        async ({ spaceName, skip, take }) => {
          const configuration = getClientConfigurationFromEnvironment();
          const client = await Client.create(configuration);
          const releaseRepository = new ReleaseRepository(client, spaceName);
    
          const releasesResponse = await releaseRepository.list({ skip, take });
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  totalResults: releasesResponse.TotalResults,
                  itemsPerPage: releasesResponse.ItemsPerPage,
                  numberOfPages: releasesResponse.NumberOfPages,
                  lastPageNumber: releasesResponse.LastPageNumber,
                  items: releasesResponse.Items.map(release => ({
                    id: release.Id,
                    version: release.Version,
                    channelId: release.ChannelId,
                    projectId: release.ProjectId,
                    releaseNotes: release.ReleaseNotes,
                    assembled: release.Assembled,
                    ignoreChannelRules: release.IgnoreChannelRules,
                    selectedPackages: release.SelectedPackages,
                    selectedGitResources: release.SelectedGitResources,
                    buildInformation: release.BuildInformation,
                    customFields: release.CustomFields
                  }))
                }),
              },
            ],
          };
        }
      );
    }
  • Registers the tool metadata in the global TOOL_REGISTRY for discovery and conditional enabling during top-level tool registration.
    registerToolDefinition({
      toolName: "list_releases",
      config: { toolset: "releases", readOnly: true },
      registerFn: registerListReleasesTool,
    });
  • Import triggers execution of registerToolDefinition in listReleases.ts, adding the tool to TOOL_REGISTRY.
    import "./listReleases.js";
Behavior3/5

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

Annotations provide readOnlyHint=true, indicating a safe read operation. The description adds behavioral context by mentioning pagination support (skip and take parameters), which is useful beyond annotations. However, it lacks details on output format, rate limits, or error conditions, leaving gaps in behavioral understanding.

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 front-loaded with the core purpose in the first sentence, followed by concise details on parameters. Both sentences are necessary and efficient, with no redundant information. It's appropriately sized for a simple listing tool.

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

Completeness3/5

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

Given the tool's low complexity and read-only nature (annotations help), the description covers basic purpose and parameters adequately. However, with no output schema, it should ideally describe return values (e.g., list of releases with fields). The lack of usage guidelines and full parameter documentation reduces completeness for agent invocation.

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 low (33%), with only 'spaceName' documented. The description compensates by explaining that spaceName is required and that skip/take are for pagination, adding meaning beyond the schema. However, it doesn't specify units or constraints for skip/take (e.g., numeric ranges), so coverage remains partial.

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 clearly states the tool's purpose as 'list releases in a given space' with a specific verb (list) and resource (releases). It distinguishes from siblings like 'list_releases_for_project' by specifying space-level listing, though not explicitly contrasting them. The title annotation reinforces this, but the description itself is adequately clear.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_releases_for_project' or 'get_release_by_id'. It mentions the required spaceName parameter but offers no context about prerequisites, typical use cases, or exclusions. This leaves the agent with minimal usage direction.

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