Skip to main content
Glama

delete_app

Destructive

Remove an application from your Codemagic account by providing its application ID.

Instructions

Delete an application from Codemagic.

Args: app_id: The Codemagic application ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes

Implementation Reference

  • The MCP tool handler for 'delete_app'. Decorated with `@mcp.tool(annotations=ToolAnnotations(destructiveHint=True))`, calls `client.delete_app(app_id)`.
    @mcp.tool(annotations=ToolAnnotations(destructiveHint=True))
    async def delete_app(app_id: str) -> Any:
        """Delete an application from Codemagic.
    
        Args:
            app_id: The Codemagic application ID.
        """
        async with CodemagicClient() as client:
            return await client.delete_app(app_id)
  • The HTTP client method that performs the DELETE request to /apps/{app_id}.
    async def delete_app(self, app_id: str) -> Any:
        return await self._delete(f"/apps/{app_id}")
  • The tool registration entry point: `register_all_tools(mcp)` calls `apps.register(mcp)`, which registers delete_app via the decorator.
    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)
  • Server calls `register_all_tools(mcp)` to register all tools including delete_app.
    register_all_tools(mcp)
  • The `delete_app` tool uses `app_id: str` as its single input parameter, defined in the function signature. It is annotated as destructive via ToolAnnotations.
    @mcp.tool(annotations=ToolAnnotations(destructiveHint=True))
Behavior3/5

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

Annotations already provide destructiveHint=true, and the description says 'Delete,' which aligns. No additional behavioral context beyond what the annotation provides, such as irreversibility or required permissions.

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?

Extremely concise: two short sentences covering purpose and parameter. No wasted words, front-loaded with the action.

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?

Given the tool's simplicity (one parameter, no output schema, destructive annotation present), the description is largely complete. Could mention that the action is irreversible, but the annotation already implies it.

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?

With 0% schema description coverage, the description adds crucial meaning: 'app_id: The Codemagic application ID.' This explains what the parameter is, making it clear despite the bare schema.

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?

Description clearly states 'Delete an application from Codemagic.' The verb 'delete' and resource 'application' are specific, and the tool is well-distinguished from siblings like add_app or list_apps.

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 vs alternatives. There is no mention of when not to use it or any prerequisites. The purpose is implied but explicit usage direction is missing.

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