Skip to main content
Glama

create_branch_deployment

Deploy selected releases to a specific branch pipeline stage by providing the branch ID and release UUIDs.

Instructions

Triggers a deployment of specified releases to a given branch (pipeline stage).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branch_idYesNumeric ID of the branch to deploy to
release_uuidsYesList of release UUIDs to deploy

Implementation Reference

  • The handler function that executes the 'create_branch_deployment' tool logic. It validates inputs (branch_id and release_uuids), POSTs to /deployments/ endpoint, and returns the JSON response.
    export function registerBranchDeployments(server: McpServer): void {
      // Tool: create_branch_deployment
      server.tool(
        'create_branch_deployment',
        'Triggers a deployment of specified releases to a given branch (pipeline stage).',
        {
          branch_id: z.number().describe('Numeric ID of the branch to deploy to'),
          release_uuids: z.array(z.string()).describe('List of release UUIDs to deploy'),
        },
        async ({ branch_id, release_uuids }) => {
          try {
            const payload = {
              branch_id,
              release_uuids,
            };
            const data = await apiPost('/deployments/', payload);
            return createJsonResponse(data);
          } catch (error) {
            if (error instanceof APIError) {
              return createErrorResponse(error);
            }
            throw error;
          }
        }
      );
    }
  • Zod schema defining the input parameters: branch_id (number) and release_uuids (array of strings).
    {
      branch_id: z.number().describe('Numeric ID of the branch to deploy to'),
      release_uuids: z.array(z.string()).describe('List of release UUIDs to deploy'),
    },
  • Registration call that wires the create_branch_deployment tool into the MCP server.
    registerBranchDeployments(server);
  • Import statement for the branch-deployments module.
    import { registerBranchDeployments } from './branch-deployments.js';
  • The apiPost helper function used by the handler to make POST requests to the Storyblok Management API.
    export async function apiPost<T = unknown>(
      path: string,
      body: unknown
    ): Promise<T> {
      const url = buildManagementUrl(path);
      const response = await fetch(url, {
        method: 'POST',
        headers: getManagementHeaders(),
        body: JSON.stringify(body),
      });
      return handleResponse<T>(response, url);
    }
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only states that it triggers a deployment but omits side effects, required permissions, error handling, or whether it overwrites existing deployments.

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?

The description is a single concise sentence with no wasted words. It is well-structured but could benefit from a bit more detail without becoming verbose.

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

Completeness2/5

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

Given the simplicity of the operation and complete schema descriptions, the description is minimally complete but lacks behavioral context such as idempotency, authentication needs, or what happens on success/failure.

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 100% with descriptions for both parameters. The description adds no additional meaning beyond the schema, which already explains the purpose of branch_id and release_uuids adequately.

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 the action (triggers a deployment), the resources (specified releases to a given branch), and clarifies that branch refers to a pipeline stage. It is distinct from sibling tools like create_branch and create_release.

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 does not specify when to use this tool over alternatives, nor does it mention prerequisites (e.g., releases must exist, branch must be a pipeline stage) or when not to use it.

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/hypescale/storyblok-mcp-server'

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