Skip to main content
Glama
OctopusDeploy

Octopus Deploy MCP Server

Official

list_releases_for_project

Read-only

Retrieve all releases for a specific project in Octopus Deploy. Use this tool to view deployment history, track versions, and manage release information within a designated space.

Instructions

List releases for a specific project

This tool lists all releases for a given project in a space. The space name and project ID are required. Optionally provide skip, take, and searchByVersion parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNameYes
projectIdYes
skipNo
takeNo
searchByVersionNoSearch releases by version string

Implementation Reference

  • The handler function that fetches and returns releases for a given project using the Octopus Deploy API.
    async ({ spaceName, projectId, skip, take, searchByVersion }) => {
      const configuration = getClientConfigurationFromEnvironment();
      const client = await Client.create(configuration);
      const releaseRepository = new ReleaseRepository(client, spaceName);
    
      const releasesResponse = await releaseRepository.listForProject(projectId, { 
        skip, 
        take, 
        searchByVersion 
      });
    
      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 using Zod for validating tool parameters.
      spaceName: z.string(),
      projectId: z.string(),
      skip: z.number().optional(),
      take: z.number().optional(),
      searchByVersion: z.string().optional().describe("Search releases by version string")
    },
  • MCP server tool registration including name, description, input schema, output metadata, and handler.
      server.tool(
        "list_releases_for_project",
        `List releases for a specific project
      
      This tool lists all releases for a given project in a space. The space name and project ID are required. Optionally provide skip, take, and searchByVersion parameters.`,
        { 
          spaceName: z.string(),
          projectId: z.string(),
          skip: z.number().optional(),
          take: z.number().optional(),
          searchByVersion: z.string().optional().describe("Search releases by version string")
        },
        {
          title: "List releases for a project in Octopus Deploy",
          readOnlyHint: true,
        },
        async ({ spaceName, projectId, skip, take, searchByVersion }) => {
          const configuration = getClientConfigurationFromEnvironment();
          const client = await Client.create(configuration);
          const releaseRepository = new ReleaseRepository(client, spaceName);
    
          const releasesResponse = await releaseRepository.listForProject(projectId, { 
            skip, 
            take, 
            searchByVersion 
          });
    
          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 in the TOOL_REGISTRY for conditional enabling based on config.
    registerToolDefinition({
      toolName: "list_releases_for_project",
      config: { toolset: "releases", readOnly: true },
      registerFn: registerListReleasesForProjectTool,
    });
Behavior3/5

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

Annotations provide readOnlyHint=true, so the agent knows this is a safe read operation. The description adds context about required parameters (spaceName, projectId) and optional pagination/search capabilities, which is useful behavioral information beyond the annotations. However, it doesn't disclose rate limits, authentication needs, or return format details.

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 efficiently structured in two sentences: the first states the core purpose, the second details parameters. Every word serves a purpose with zero redundancy, making it easy for an agent to parse quickly.

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?

For a list operation with readOnlyHint annotation, the description covers the essential scope (project-specific) and parameters adequately. However, with no output schema, it doesn't describe the return format (e.g., what fields releases include), which could help the agent understand the data structure. The low schema coverage is partially mitigated by the parameter listing.

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 (20%), with only 'searchByVersion' having a description. The description compensates by listing all parameters (spaceName, projectId, skip, take, searchByVersion) and indicating which are required versus optional, adding meaningful context beyond the bare schema. However, it doesn't explain parameter formats or constraints.

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: 'List releases for a specific project' with the resource 'releases' and scope 'for a given project in a space'. It distinguishes from the sibling 'list_releases' by specifying project-scoping, but doesn't explicitly contrast with 'get_release_by_id' or other siblings.

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

Usage Guidelines3/5

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

The description implies usage context ('for a given project in a space') and mentions optional parameters for pagination/search, but provides no explicit guidance on when to use this tool versus alternatives like 'list_releases' or 'get_release_by_id'. The agent must infer from the project-scoping.

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