Skip to main content
Glama
OctopusDeploy

Octopus Deploy MCP Server

Official

get_release_by_id

Read-only

Retrieve detailed information about a specific Octopus Deploy release using its unique identifier and space name to inspect deployment status and configuration.

Instructions

Get details for a specific release by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceNameYesThe space name
releaseIdYesThe ID of the release to retrieve

Implementation Reference

  • The core handler logic that authenticates with Octopus Deploy, fetches the specific release by ID using the ReleaseRepository, extracts key fields, and returns them as JSON-formatted text content.
    async ({ spaceName, releaseId }) => {
      const configuration = getClientConfigurationFromEnvironment();
      const client = await Client.create(configuration);
      const releaseRepository = new ReleaseRepository(client, spaceName);
    
      const release = await releaseRepository.get(releaseId);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              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 spaceName and releaseId parameters, along with output description metadata indicating read-only access.
    { 
      spaceName: z.string().describe("The space name"),
      releaseId: z.string().describe("The ID of the release to retrieve")
    },
    {
      title: "Get release details by ID from Octopus Deploy",
      readOnlyHint: true,
    },
  • The server.tool call within registerGetReleaseByIdTool that registers the tool with name, description, input schema, output metadata, and handler on the MCP server.
      server.tool(
        "get_release_by_id",
        "Get details for a specific release by its ID",
        { 
          spaceName: z.string().describe("The space name"),
          releaseId: z.string().describe("The ID of the release to retrieve")
        },
        {
          title: "Get release details by ID from Octopus Deploy",
          readOnlyHint: true,
        },
        async ({ spaceName, releaseId }) => {
          const configuration = getClientConfigurationFromEnvironment();
          const client = await Client.create(configuration);
          const releaseRepository = new ReleaseRepository(client, spaceName);
    
          const release = await releaseRepository.get(releaseId);
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  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
                }),
              },
            ],
          };
        }
      );
    }
  • Self-registration of the tool definition into the TOOL_REGISTRY, specifying toolset 'releases' and read-only, linking to the register function.
    registerToolDefinition({
      toolName: "get_release_by_id",
      config: { toolset: "releases", readOnly: true },
      registerFn: registerGetReleaseByIdTool,
    });
  • Import statement in the tools index that loads the getReleaseById module, triggering its TOOL_REGISTRY registration.
    import "./getReleaseById.js";
Behavior3/5

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

Annotations already provide readOnlyHint=true and a title, so the description doesn't need to repeat safety aspects. It adds minimal context by specifying 'by its ID', but doesn't disclose behavioral traits like error handling, rate limits, or authentication needs beyond what annotations cover.

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 a single, efficient sentence with zero waste—it directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy 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?

Given the simple read operation with annotations covering safety and full schema coverage, the description is adequate but minimal. It doesn't explain return values or error cases, which could be helpful since there's no output schema, leaving some gaps in completeness.

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?

With 100% schema description coverage, the input schema fully documents both parameters (spaceName and releaseId). The description doesn't add any additional meaning or context about these parameters beyond what's in the schema, so it meets the baseline for high coverage.

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 verb 'Get details' and resource 'specific release by its ID', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_task_by_id' or 'get_tenant_by_id' that follow similar patterns, missing full sibling distinction.

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' or 'list_releases_for_project'. It lacks context about prerequisites, such as needing the space name, and doesn't mention any exclusions or specific use cases.

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