Skip to main content
Glama
AgiMaulana

Codemagic

by AgiMaulana
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_cache

Destructive

Remove a specific build cache for a Codemagic application to free storage space and resolve cache-related issues by providing the app ID and cache ID.

Instructions

Delete a specific build cache for a Codemagic application.

Args: app_id: The Codemagic application ID. cache_id: The cache ID to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes
cache_idYes

Implementation Reference

  • codemagic_mcp/tools/caches.py:30-39 (handler)
    The MCP tool registration and handler for `delete_cache`. It calls the `CodemagicClient.delete_cache` method.
    @mcp.tool(annotations=ToolAnnotations(destructiveHint=True))
async def delete_cache(app_id: str, cache_id: str) -> Any:
    """Delete a specific build cache for a Codemagic application.

    Args:
        app_id: The Codemagic application ID.
        cache_id: The cache ID to delete.
    """
    async with CodemagicClient() as client:
        return await client.delete_cache(app_id, cache_id)
  • codemagic_mcp/client.py:340-341 (handler)
    The underlying API client method that performs the actual HTTP DELETE request to the Codemagic API to delete a cache.
    async def delete_cache(self, app_id: str, cache_id: str) -> Any:
    return await self._delete(f"/apps/{app_id}/caches/{cache_id}")

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

Annotations indicate destructiveHint=true, which aligns with the description. The description adds context about Codemagic applications but omits behavioral details like irreversibility, immediate effect on running builds, or return value indicators.

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 structure with a clear single-sentence purpose statement followed by an Args block. No redundant information, though the docstring format (Args:) could be more conventional prose for MCP descriptions.

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?

Adequate for a 2-parameter deletion tool: covers resource, scope, and parameters. However, given the destructive nature and lack of output schema, it should ideally confirm the permanence of deletion or indicate what success/failure looks like.

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?

With 0% schema description coverage, the Args section fully compensates by documenting both required parameters: 'app_id' is clarified as 'The Codemagic application ID' and 'cache_id' as 'The cache ID to delete', providing necessary semantic context missing from the bare schema titles.

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?

Clear verb (Delete) + resource (build cache) + scope (specific, for Codemagic application). The word 'specific' implicitly distinguishes it from sibling 'delete_all_caches', though it doesn't explicitly name the alternative.

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 explicit guidance on when to use this versus 'delete_all_caches' or other cache management tools. The term 'specific' implies targeted use, but lacks explicit 'when to use/when not' instructions or prerequisites.

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