Skip to main content
Glama
AgiMaulana

Codemagic

by AgiMaulana
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_build

Retrieve details and status of a specific Codemagic CI/CD build, including step summary counts and optional full step lists for log access.

Instructions

Get details and status of a specific Codemagic build.

Always includes a step summary (total, success, failed, skipped counts). Set include_steps=True to also get the full list of steps with their IDs, which can then be used with get_step_logs.

Args: build_id: The Codemagic build ID. include_steps: If True, include full step list with IDs. Default False.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
build_idYes
include_stepsNo

Implementation Reference

  • codemagic_mcp/tools/builds.py:32-45 (handler)
    The 'get_build' tool handler, defined using the FastMCP decorator, which calls the CodemagicClient's get_build method.
    @mcp.tool()
async def get_build(build_id: str, include_steps: bool = False) -> Any:
    """Get details and status of a specific Codemagic build.

    Always includes a step summary (total, success, failed, skipped counts).
    Set include_steps=True to also get the full list of steps with their IDs,
    which can then be used with get_step_logs.

    Args:
        build_id: The Codemagic build ID.
        include_steps: If True, include full step list with IDs. Default False.
    """
    async with CodemagicClient() as client:
        return await client.get_build(build_id, include_steps=include_steps)
  • codemagic_mcp/tools/builds.py:9-9 (registration)
    The tool is registered by the 'register' function which takes an MCP instance and decorates the tool handlers with '@mcp.tool()'.
    def register(mcp: FastMCP) -> None:

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses specific response content ('Always includes a step summary with total, success, failed, skipped counts') and the relationship between include_steps parameter and subsequent tool usage. Does not mention auth requirements or error states.

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, followed by behavioral disclosure and parameter documentation. Args section is necessary given zero schema coverage. No redundant sentences, though slightly verbose due to embedded parameter docs.

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?

Appropriately complete for a 2-parameter read operation without output schema. Documents the fixed response payload (step summary counts) and critical sibling relationship (get_step_logs). Lacking only explicit guidance differentiating from get_build_logs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (titles only, no descriptions). The Args block fully compensates by documenting both parameters: build_id as 'The Codemagic build ID' and include_steps with behavior, default value, and downstream use case. Essential semantic information provided.

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?

Clear specific verb (Get) + resource (build details/status) + scope (specific Codemagic build). Explicitly distinguishes from sibling get_step_logs by noting this tool's output 'can then be used with get_step_logs', establishing the workflow boundary.

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

Usage Guidelines4/5

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

Provides explicit workflow guidance linking include_steps=True output to get_step_logs usage. Explains conditional behavior (step summary always included vs full steps when flag set). Lacks explicit comparison to get_build_logs for when to prefer each.

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