Skip to main content
Glama

trigger_build

Trigger a new build on Codemagic by providing the app ID and workflow ID, with optional environment variables and inline YAML.

Instructions

Trigger a new build on Codemagic. For release builds: determine BUILD_NUMBER first using list_asc_builds (iOS) or list_google_play_tracks (Android), then pass it in the variables parameter. Use yaml_content to supply an inline codemagic.yaml — get a starter template from get_yaml_template and validate it with validate_codemagic_yaml before triggering. Call wait_for_build with the returned build ID to wait for completion and retrieve artifact URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYesThe application ID
workflow_idYesThe workflow ID to run
branchNoGit branch to build
tagNoGit tag to build
variablesNoEnvironment variables to inject into the build
groupsNoEnvironment variable groups to include
labelsNoLabels to attach to the build
yaml_contentNoA codemagic.yaml file content to use for this build. When provided, the yaml is passed inline and does not need to exist in the repository.
instance_typeNoOverride the instance type for this build. Common values: mac_mini_m2, mac_mini_m4, linux_x2, linux_x4, windows_x2. Must be available on your billing plan. If omitted, the instance type from codemagic.yaml is used. IMPORTANT: Personal accounts (no team) can only use mac_mini_m2 — linux_x2, linux_x4, and mac_mini_m4 are not available on personal accounts.
Behavior3/5

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

Annotations are minimal (non-readonly, non-destructive). Description adds workflow context (validate yaml, wait for build) but does not disclose error cases, rate limits, or permission requirements. It explains yaml passing mechanism but lacks transparency on build costs or time.

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?

Single paragraph front-loaded with main purpose, then details. Every sentence adds value, but could be structured with bullet points for readability. No wasted words, but slightly dense.

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?

Given complexity (9 params, no output schema), description covers core usage flow and companion tools. Lacks return value format and error handling. Since no output schema, should describe response structure minimally.

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?

Schema coverage is 100% with parameter descriptions. Description adds extra meaning: explains how to use variables for BUILD_NUMBER in release builds, and specifies instance_type restrictions for personal accounts. Compensates for schema's lack of enums or detailed formats.

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 'Trigger a new build on Codemagic' with specific verb and resource. It distinguishes from siblings by referencing companion tools like wait_for_build, get_yaml_template, and validate_codemagic_yaml.

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 guidelines: for release builds, determine BUILD_NUMBER first; use yaml_content with validation; call wait_for_build after. Mentions alternatives indirectly but does not explicitly state when not to use this tool.

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/todah-zg/codemagic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server