Skip to main content
Glama

list_build_artifacts

Retrieve all artifacts generated during a Codemagic build by providing the build ID to access outputs like APKs, IPAs, or logs.

Instructions

List all artifacts produced by a Codemagic build.

Args: build_id: The Codemagic build ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
build_idYes

Implementation Reference

  • The core implementation of list_build_artifacts which calls the Codemagic API.
    async def list_build_artifacts(self, build_id: str) -> Any:
        build = await self._get(f"/builds/{build_id}")
        artifacts = build.get("build", {}).get("artefacts", [])
        return [
            {
                "name": a.get("name"),
                "type": a.get("type"),
                "url": a.get("url"),
                "size": a.get("size"),
                "version": a.get("versionName") or a.get("version"),
                "versionCode": a.get("versionCode"),
                "minOsVersion": a.get("minOsVersion"),
            }
            for a in artifacts
        ]
  • The MCP tool registration for list_build_artifacts.
    @mcp.tool()
    async def list_build_artifacts(build_id: str) -> Any:
        """List all artifacts produced by a Codemagic build.
    
        Args:
            build_id: The Codemagic build ID.
        """
        async with CodemagicClient() as client:
            return await client.list_build_artifacts(build_id)
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. While 'List' implies read-only safety, it omits pagination behavior, return format structure, error conditions (e.g., invalid build_id), and rate limits.

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?

Efficient docstring format with purpose statement followed by Args block. Well-structured and appropriately sized for a single-parameter tool, with no wasted words while still compensating for schema deficiencies.

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?

Simple tool (1 parameter) but significant gaps remain: no output schema exists and description doesn't describe the returned artifact metadata structure, available filters, or relationship to artifact download workflows. Lacks completeness expected when annotations are absent.

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?

With 0% schema coverage (schema lacks description fields), the Args section adds necessary semantic context by identifying build_id as 'The Codemagic build ID', clarifying the ID type. However, it doesn't specify format, constraints, or how to obtain the ID.

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?

Uses specific verb 'List' with clear resource 'artifacts' and scope 'produced by a Codemagic build'. Implicitly distinguishes from siblings like `get_artifact_url` (singular retrieval) and `create_artifact_public_url` (mutation) by emphasizing enumeration of all artifacts.

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?

Provides no guidance on when to use this versus `get_artifact_url` or prerequisites such as build completion status. No mention of workflow context (e.g., call after `get_build` to obtain build_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