Skip to main content
Glama

list_apps

Retrieve all applications in your Codemagic account to manage builds and deployments.

Instructions

List all applications in your Codemagic account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'list_apps'. It creates a CodemagicClient and delegates to client.list_apps().
    async def list_apps() -> Any:
        """List all applications in your Codemagic account."""
        async with CodemagicClient() as client:
            return await client.list_apps()
  • No input schema is defined since list_apps takes no arguments; it returns Any.
    async def list_apps() -> Any:
  • Registration of list_apps via @mcp.tool() decorator inside the register() function, which is called from register_all_tools() in tools/__init__.py, then from server.py.
    def register(mcp: FastMCP) -> None:
        @mcp.tool()
        async def list_apps() -> Any:
            """List all applications in your Codemagic account."""
            async with CodemagicClient() as client:
                return await client.list_apps()
  • The client. list_apps() helper method: sends GET /apps, extracts applications from the response, trims each app via _trim_app() and returns the list.
    async def list_apps(self) -> Any:
        data = await self._get("/apps")
        apps = data.get("applications", data) if isinstance(data, dict) else data
        if isinstance(apps, list):
            return [self._trim_app(a) for a in apps]
        return apps
  • The _trim_app() helper used by list_apps to normalize app data into a consistent shape.
    def _trim_app(self, app: dict) -> dict:
        repo = app.get("repository") or {}
        return {
            "_id": app.get("_id"),
            "appName": app.get("appName"),
            "projectType": app.get("projectType"),
            "archived": app.get("archived"),
            "isConfigured": app.get("isConfigured"),
            "lastBuildId": app.get("lastBuildId"),
            "createdAt": app.get("createdAt"),
            "repository": {
                "url": repo.get("htmlUrl"),
                "provider": repo.get("provider"),
                "defaultBranch": repo.get("defaultBranch"),
                "language": repo.get("language"),
            },
        }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'list' but does not disclose if authentication is needed, rate limits, or any side effects. For a read operation, it should at least imply safety.

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?

The description is a single sentence with no wasted words, fitting the simple nature of the tool.

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

Completeness3/5

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

The description is minimal. Given no output schema, it does not explain what fields are returned or if pagination exists. A list tool often needs more detail for agents.

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?

The input schema has zero parameters with 100% coverage. Description adds no param info, but the baseline for 0 params is 4. It does not need to explain parameters.

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 'List all applications' using a specific verb and resource. It distinguishes from sibling tools like add_app (create) and get_app (single app).

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?

No explicit guidance on when to use or not use this tool. Usage is implied by its simplicity, but there is no mention of alternatives or context.

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