Skip to main content
Glama

Set Env Var Across Multiple Applications

coolify_bulk_set_app_env
Idempotent

Set one environment variable across multiple applications simultaneously. Ideal for rotating shared secrets, with per-app success/failure reporting and non-blocking errors.

Instructions

Upsert ONE environment variable (key/value) across many applications at once. Useful for rotating a shared secret. Returns a per-app success/failure summary; a failure on one app does not stop the others.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesVariable name
valueYesVariable value
revealNoReveal redacted secret values in the response (default false; the call is audited)
instanceYesREQUIRED — which Coolify instance to mutate: 'prod' (Hetzner VPS) or 'dev' (local OrbStack VM). No default: state the target explicitly so a write never lands on prod by accident.
app_uuidsYesApplication UUIDs to update
is_runtimeNoAvailable at runtime
is_buildtimeNoAvailable at build time
Behavior5/5

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

Discloses non-all-or-nothing behavior (partial failures), audit logging for reveal parameter, and safety warning on instance parameter. Adds significant value beyond annotations (readOnlyHint, destructiveHint, idempotentHint).

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?

Two compact sentences cover purpose, use case, and return behavior. No superfluous words. Front-loaded with key action and scope.

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

Completeness5/5

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

Covers all essential behavioral aspects (return format, partial failure, safety on instance, audit) for a bulk mutation tool with 7 parameters and no output schema. No gaps identified.

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 baseline applies. The description does not add new parameter details but the schema itself is clear. No additional parameter semantics needed.

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?

Explicitly states the verb (upsert), resource (environment variable), and scope (across many applications). Distinguishes from sibling tools like coolify_create_app_env which operate on single apps.

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?

Provides a clear use case (rotating a shared secret) and implies suitability for bulk operations. Lacks explicit comparison to sibling tools for single-app or multi-variable scenarios, but context is strong.

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/AlobarQuest/infraops-mcp-server'

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