Skip to main content
Glama

update_variable

Modify environment variables in Codemagic CI/CD applications to configure build settings, update secrets, or adjust deployment parameters.

Instructions

Update an existing environment variable for a Codemagic application.

Args: app_id: The Codemagic application ID. variable_id: The variable ID to update. key: The variable name. value: The new variable value. group: The variable group name. secure: Whether the variable should be encrypted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes
variable_idYes
keyYes
valueYes
groupYes
secureNo

Implementation Reference

  • The tool handler definition for `update_variable` in the MCP server tools, which invokes the `CodemagicClient`.
    async def update_variable(
        app_id: str,
        variable_id: str,
        key: str,
        value: str,
        group: str,
        secure: bool = False,
    ) -> Any:
        """Update an existing environment variable for a Codemagic application.
    
        Args:
            app_id: The Codemagic application ID.
            variable_id: The variable ID to update.
            key: The variable name.
            value: The new variable value.
            group: The variable group name.
            secure: Whether the variable should be encrypted.
        """
        async with CodemagicClient() as client:
            return await client.update_variable(
                app_id=app_id,
                variable_id=variable_id,
                key=key,
                value=value,
                group=group,
                secure=secure,
            )
  • The underlying API client implementation for updating a variable, which performs the PUT request to the Codemagic API.
    async def update_variable(
        self,
        app_id: str,
        variable_id: str,
        key: str,
        value: str,
        group: str,
        secure: bool = False,
    ) -> Any:
        return await self._put(
            f"/apps/{app_id}/variables/{variable_id}",
            json={"key": key, "value": value, "group": group, "secure": secure},
        )
Behavior2/5

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

With no annotations provided, description carries full burden. It mentions encryption behavior for 'secure' parameter, but lacks critical mutation context: what happens if the variable doesn't exist, what the return value contains, or whether changes are reversible. Only minimal behavioral disclosure.

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?

Well-structured with purpose front-loaded in the first sentence, followed by necessary Args documentation. The Args section is required given 0% schema coverage, so verbosity is justified. No redundant or wasted sentences.

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?

For a 6-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description provides only baseline information. Missing error handling, return structure, and workflow prerequisites needed for safe agent invocation.

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 description coverage is 0%, so description fully compensates by documenting all 6 parameters in the Args section. Descriptions are basic (e.g., 'The variable name') but sufficient given the schema deficiencies.

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?

Clear specific verb ('Update') + resource ('environment variable') + scope ('Codemagic application'). The word 'existing' implicitly distinguishes from sibling 'add_variable', though it could more explicitly contrast when to update vs. add.

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?

No explicit guidance on when to use this versus 'add_variable', nor mention that 'variable_id' must be obtained from 'list_variables' first. No prerequisites or exclusion criteria stated.

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/AgiMaulana/CodemagicMcp'

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