Skip to main content
Glama
AgiMaulana

Codemagic

by AgiMaulana
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

add_app

Add a new public repository to Codemagic by providing its HTTPS URL. Start building and managing apps from that repository.

Instructions

Add a new public repository to Codemagic.

Args: repository_url: The HTTPS URL of the public Git repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repository_urlYes

Implementation Reference

  • codemagic_mcp/tools/apps.py:27-34 (handler)
    MCP tool handler for 'add_app' that accepts a repository_url and delegates to the CodemagicClient.
    async def add_app(repository_url: str) -> Any:
    """Add a new public repository to Codemagic.

    Args:
        repository_url: The HTTPS URL of the public Git repository.
    """
    async with CodemagicClient() as client:
        return await client.add_app(repository_url)
  • codemagic_mcp/tools/apps.py:28-31 (schema)
    Docstring serving as the schema/description for the add_app tool, defining the repository_url parameter.
    """Add a new public repository to Codemagic.

Args:
    repository_url: The HTTPS URL of the public Git repository.
  • codemagic_mcp/client.py:78-79 (helper)
    CodemagicClient.add_app helper that POSTs to /apps with {'repositoryUrl': repository_url}.
    async def add_app(self, repository_url: str) -> Any:
    return await self._post("/apps", json={"repositoryUrl": repository_url})
  • codemagic_mcp/tools/__init__.py:6-12 (registration)
    Registration entry point: register_all_tools() calls apps.register(mcp) which registers add_app via @mcp.tool().
    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)
  • codemagic_mcp/server.py:43-43 (registration)
    Server calls register_all_tools(mcp) to register all tools including add_app on the FastMCP instance.
    register_all_tools(mcp)

Tool Definition Quality

B3.4/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as duplicate handling, authentication needs, or side effects. The minimal description leaves significant gaps.

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 brief and to the point, with a clear structure (description followed by Args). No unnecessary words, though it could be slightly more structured.

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?

For a simple tool with one parameter and no output schema, the description is adequate but lacks behavioral details and usage context. It does not explain return values or potential errors.

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 0% parameter description coverage, but the Arg block adds context: 'The HTTPS URL of the public Git repository.' This provides meaning beyond the schema's title alone.

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 action ('Add') and the specific resource ('a new public repository to Codemagic'), distinguishing it from the sibling 'add_private_app' tool.

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?

No guidance on when to use this tool versus alternatives (e.g., 'add_private_app'), nor any prerequisites or exclusions. The description only states what it does.

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