Skip to main content
Glama

delete_variable

Destructive

Remove environment variables from Codemagic applications to manage configuration and maintain security by eliminating unused or sensitive data.

Instructions

Delete an environment variable from a Codemagic application.

Args: app_id: The Codemagic application ID. variable_id: The variable ID to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes
variable_idYes

Implementation Reference

  • The MCP tool handler for 'delete_variable', which calls the underlying client method.
    async def delete_variable(app_id: str, variable_id: str) -> Any:
        """Delete an environment variable from a Codemagic application.
    
        Args:
            app_id: The Codemagic application ID.
            variable_id: The variable ID to delete.
        """
        async with CodemagicClient() as client:
            return await client.delete_variable(app_id, variable_id)
  • The underlying API client method that performs the actual HTTP DELETE request to Codemagic.
    async def delete_variable(self, app_id: str, variable_id: str) -> Any:
        return await self._delete(f"/apps/{app_id}/variables/{variable_id}")
Behavior3/5

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

The annotations already declare destructiveHint: true, and the description confirms this is a delete operation. However, it adds minimal additional behavioral context beyond the annotations, failing to specify whether deletion is permanent, immediate, or if it affects running builds.

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 appropriately concise with no wasted words. The single declarative sentence followed by an Args block is efficiently structured, though the Args format is slightly unconventional for MCP tool descriptions compared to integrated prose.

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 the tool's simplicity (2 string parameters, destructive operation) and the presence of the destructiveHint annotation, the description provides sufficient context for invocation. It adequately covers the parameters and purpose, though it could explicitly note that the operation is irreversible.

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?

With 0% schema description coverage, the description compensates by documenting both parameters in the Args block: app_id is 'The Codemagic application ID' and variable_id is 'The variable ID to delete.' This adds essential semantic meaning missing from the raw 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 specific action ('Delete'), resource ('environment variable'), and scope ('Codemagic application'). It effectively distinguishes from siblings like add_variable, update_variable, and list_variables through its precise verb and object.

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

Usage Guidelines3/5

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

The description implies usage by requiring specific identifiers (app_id, variable_id), but provides no explicit guidance on when to use this tool versus alternatives like update_variable, or prerequisites such as needing to call list_variables first to obtain the variable_id.

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