Skip to main content
Glama

list_variables

Retrieve all environment variables configured for a Codemagic application. Input the app ID to get a complete list.

Instructions

List all environment variables for a Codemagic application.

Args: app_id: The Codemagic application ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes

Implementation Reference

  • The MCP tool handler for 'list_variables'. Defines the function decorated with @mcp.tool() that accepts an app_id and delegates to the client.
    async def list_variables(app_id: str) -> Any:
        """List all environment variables for a Codemagic application.
    
        Args:
            app_id: The Codemagic application ID.
        """
        async with CodemagicClient() as client:
            return await client.list_variables(app_id)
  • The CodemagicClient method that sends a GET request to /apps/{app_id}/variables to fetch the list of environment variables.
    async def list_variables(self, app_id: str) -> Any:
        return await self._get(f"/apps/{app_id}/variables")
  • The registration hub that calls variables.register(mcp), which registers the list_variables tool (among others) via the @mcp.tool() decorator.
    def register_all_tools(mcp: FastMCP) -> None:
        apps.register(mcp)
        builds.register(mcp)
        artifacts.register(mcp)
        caches.register(mcp)
        variables.register(mcp)
        webhooks.register(mcp)
  • Server entry point that calls register_all_tools(mcp) on line 43, which triggers the registration of list_variables.
    def main() -> None:
        mcp.run(transport="stdio")
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read-only list operation but does not disclose potential side effects, permissions needed, pagination, or response format details.

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 very short with two sentences plus an argument list. It is not wordy but could be slightly improved by integrating the argument description more seamlessly.

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?

Given the absence of output schema and annotations, the description does not fully inform the agent about the return structure (e.g., list of variable names and values) or error conditions, leaving gaps for a simple list tool.

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 coverage is 0%, so the description must compensate. It adds 'The Codemagic application ID' for app_id, which provides basic meaning beyond the schema title. However, it lacks details like format or how to obtain it.

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 verb 'List' and the resource 'all environment variables for a Codemagic application.' It distinguishes from sibling tools like add_variable, delete_variable, etc.

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?

The description gives the required argument app_id but does not provide guidance on when to use this tool versus alternatives like get_app or list_apps, nor does it specify any conditions for use.

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