Skip to main content
Glama
imprezahost

Impreza Host MCP Server

impreza_redeploy_deployment

Rebuild a custom deployment in place from its current source, re-pulling the image or git ref, and swap the container with near-zero downtime while preserving domain and host port. Optionally update environment variables without teardown.

Instructions

Rebuild a CUSTOM deployment in place from its current source — re-pull the image, re-clone the watched git ref at its new HEAD, or rebuild — and swap the container with near-zero downtime. Reuses the same deployment, so the domain, host port, and URL never change. This is the in-place way to ship a new build of a running custom app the customer changed — PREFER it over uninstall + recreate. Optional vars are merged into the stored environment before the rebuild (rotate a secret / add a var without a teardown); system vars (DEPLOYMENT_ID, DOMAIN_URL, HOST_PORT, ...) are preserved. The source itself is not changed here — to change the image ref or git URL, recreate under the same name (the *.imprezaapps.com domain is preserved either way). Custom deployments only; returns the deployment flipped to updating — poll impreza_list_deployments for running/failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
varsNoOptional env vars merged into the deployment before the rebuild. System vars are preserved.
deployment_idYesThe dpl_... id of the custom deployment to rebuild.
Behavior4/5

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

No annotations provided, but the description covers key behaviors: near-zero downtime, source unchanged, vars merge, system vars preserved, returns 'updating' state. Could mention failure implications or auth requirements.

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?

Three sentences, front-loaded with primary action. Slightly verbose but still efficient and well-structured.

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

Completeness4/5

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

Given no annotations or output schema, the description adequately explains purpose, behavior, parameter context, and return indicator. Could note failure handling or prerequisites for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% with descriptions. The description adds meaning by explaining 'vars' effect (merged, system vars preserved) and deployment_id format (dpl_...), going beyond schema.

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 tool does an in-place rebuild of a custom deployment, reusing the same deployment and preserving domain/URL. It distinguishes from uninstall+recreate by explicitly preferring this tool for shipping new builds.

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

Usage Guidelines5/5

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

The description explicitly says 'PREFER it over uninstall + recreate' and explains when to recreate instead (to change image ref or git URL), providing clear guidance on tool selection.

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/imprezahost/impreza-mcp'

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