Skip to main content
Glama
heroku

Heroku MCP server

Official
by heroku

pipelines_promote

Promote applications through pipeline stages to deploy code, manage staged releases, coordinate multi-app promotions, and control deployment workflows. Simplifies safe app promotion between environments.

Instructions

Promote applications through pipeline stages. Use this tool when you need to: 1) Deploy code to staging or production environments, 2) Manage staged releases, 3) Coordinate multi-app promotions, 4) Control deployment workflows. The tool handles safe promotion of apps between pipeline stages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appYesName of the app to promote from
toNocomma separated list of apps to promote to

Implementation Reference

  • The main handler function for the 'pipelines_promote' tool. It constructs a CommandBuilder for 'pipelines:promote', adds app and to flags from options, executes via herokuRepl, and returns handled CLI output.
    async (options: PipelinesPromoteOptions): Promise<McpToolResponse> => {
      const command = new CommandBuilder(TOOL_COMMAND_MAP.PIPELINES_PROMOTE)
        .addFlags({
          app: options.app,
          to: options.to
        })
        .build();
    
      const output = await herokuRepl.executeCommand(command);
      return handleCliOutput(output);
    }
  • Zod schema defining input parameters for the pipelines_promote tool: app (required string), to (optional string). Used for validation in tool registration.
    export const pipelinesPromoteOptionsSchema = z.object({
      app: z.string().describe('Source app for promotion'),
      to: z.string().optional().describe('Target apps for promotion (comma-separated)')
    });
  • Registration function that calls server.tool() to register 'pipelines_promote' with name, description, input schema, and handler function on the MCP server.
    export const registerPipelinesPromoteTool = (server: McpServer, herokuRepl: HerokuREPL): void => {
      server.tool(
        'pipelines_promote',
        'Promotes apps between pipeline stages with configurable target applications',
        pipelinesPromoteOptionsSchema.shape,
        async (options: PipelinesPromoteOptions): Promise<McpToolResponse> => {
          const command = new CommandBuilder(TOOL_COMMAND_MAP.PIPELINES_PROMOTE)
            .addFlags({
              app: options.app,
              to: options.to
            })
            .build();
    
          const output = await herokuRepl.executeCommand(command);
          return handleCliOutput(output);
        }
      );
    };
  • src/index.ts:94-94 (registration)
    The call to registerPipelinesPromoteTool during MCP server initialization, passing server and herokuRepl instances.
    pipelines.registerPipelinesPromoteTool(server, herokuRepl);
  • Constant in TOOL_COMMAND_MAP that maps to the Heroku CLI command 'pipelines:promote' used by the handler.
    PIPELINES_PROMOTE: 'pipelines:promote',
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'safe promotion' and implies mutation (promoting/deploying), but lacks details on permissions required, whether promotions are reversible, rate limits, error handling, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized and front-loaded: it starts with the core purpose, then lists usage scenarios in a bullet-like format, and ends with a summary sentence. Every sentence adds value without redundancy, making it efficient and well-structured.

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 complexity (mutation with 2 parameters), no annotations, and no output schema, the description is moderately complete. It covers purpose and usage well but lacks behavioral details like side effects, error cases, or return values. It compensates somewhat with clear guidelines but falls short of fully addressing the gaps in transparency and output expectations.

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 100%, so the schema already documents both parameters ('app' and 'to'). The description adds some context by mentioning 'promote applications through pipeline stages' and 'multi-app promotions,' which aligns with the parameters, but doesn't provide additional syntax, format details, or examples beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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: 'Promote applications through pipeline stages' and 'handles safe promotion of apps between pipeline stages.' It uses specific verbs ('promote,' 'deploy,' 'manage,' 'coordinate') and identifies the resource ('applications,' 'apps'), but doesn't explicitly distinguish it from sibling tools like 'deploy_to_heroku' or 'pipelines_create' beyond the pipeline context.

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 provides explicit usage scenarios: 'Use this tool when you need to: 1) Deploy code to staging or production environments, 2) Manage staged releases, 3) Coordinate multi-app promotions, 4) Control deployment workflows.' This gives clear context for when to use it, though it doesn't explicitly state when NOT to use it or name alternatives among siblings like 'deploy_to_heroku' for direct deployment.

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

Related 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/heroku/heroku-mcp-server'

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