Skip to main content
Glama
AgiMaulana

Codemagic

by AgiMaulana
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_artifact_url

Retrieve the download URL for a build artifact using its secure filename from Codemagic CI/CD results.

Instructions

Get the download URL for a build artifact.

Args: secure_filename: The secure filename of the artifact (from build results).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secure_filenameYes

Implementation Reference

  • codemagic_mcp/tools/artifacts.py:10-17 (handler)
    The MCP tool definition and handler for get_artifact_url.
    async def get_artifact_url(secure_filename: str) -> Any:
    """Get the download URL for a build artifact.

    Args:
        secure_filename: The secure filename of the artifact (from build results).
    """
    async with CodemagicClient() as client:
        return await client.get_artifact_url(secure_filename)
  • codemagic_mcp/client.py:272-273 (handler)
    The actual API client method that performs the network request for get_artifact_url.
    async def get_artifact_url(self, secure_filename: str) -> Any:
    return await self._get(f"/artifacts/{secure_filename}")
  • codemagic_mcp/tools/artifacts.py:8-8 (registration)
    Registration of the get_artifact_url tool with the MCP server.
    def register(mcp: FastMCP) -> None:

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

Zero annotations provided, yet description lacks critical behavioral details: URL expiry/temporariness, authentication requirements, whether URL is pre-signed, and how it differs from the public URL sibling. Only states the retrieval action.

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?

Perfectly front-loaded with one-line purpose statement followed by Args documentation. No redundant text or wasted sentences.

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 single-parameter tool, but gaps remain: no indication of return value format (string? object?), URL lifespan, or relationship to 'create_artifact_public_url'. Given no output schema, should clarify these behavioral aspects.

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 has 0% description coverage (only 'title' field), but description compensates well by explaining 'secure_filename' comes 'from build results' and represents the secure identifier needed to locate the artifact.

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 ('Get') and resource ('download URL for a build artifact'), but fails to distinguish from sibling 'create_artifact_public_url' which likely has different semantics (temporary vs public, retrieve vs generate).

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?

Only implicit guidance through '(from build results)' in Args section suggesting prerequisite context. No explicit when-to-use guidance or comparison to alternatives like 'create_artifact_public_url'.

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