Skip to main content
Glama

create_artifact_public_url

Generate a time-limited public URL for a build artifact to share access temporarily.

Instructions

Create a time-limited public URL for a build artifact.

Args: secure_filename: The secure filename of the artifact (from build results). expires_at: Expiry time as a UNIX timestamp (seconds since epoch).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secure_filenameYes
expires_atYes

Implementation Reference

  • Tool handler function that creates a time-limited public URL for a build artifact. Decorated with @mcp.tool(), delegates to CodemagicClient.
    @mcp.tool()
    async def create_artifact_public_url(
        secure_filename: str, expires_at: int
    ) -> Any:
        """Create a time-limited public URL for a build artifact.
    
        Args:
            secure_filename: The secure filename of the artifact (from build results).
            expires_at: Expiry time as a UNIX timestamp (seconds since epoch).
        """
        async with CodemagicClient() as client:
            return await client.create_artifact_public_url(secure_filename, expires_at)
  • Client helper method that makes the actual HTTP POST request to /artifacts/{secure_filename}/public-url with the expiresAt payload.
    async def create_artifact_public_url(
        self, secure_filename: str, expires_at: int
    ) -> Any:
        return await self._post(
            f"/artifacts/{secure_filename}/public-url",
            json={"expiresAt": expires_at},
        )
  • Input schema: takes secure_filename (str) and expires_at (int, UNIX timestamp).
    async def create_artifact_public_url(
        secure_filename: str, expires_at: int
    ) -> Any:
  • Registration orchestrator: artifacts.register(mcp) is called here, which registers the create_artifact_public_url tool via the @mcp.tool() 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)
Behavior2/5

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

The description explains the time-limited nature and the parameters but fails to disclose side effects (e.g., whether it overwrites previous URLs), required permissions, error conditions, or rate limits. With no annotations, this 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, with a clear purpose statement followed by parameter explanations. Every sentence adds value, and the format is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should explain the return value (e.g., the generated URL) or any side effects. It also lacks context on authentication, expiration behavior, and prerequisites. The minimal information leaves the tool under-specified.

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?

Both parameters are described: secure_filename as 'from build results' and expires_at as 'UNIX timestamp (seconds since epoch).' This adds meaning beyond the schema (which only provides titles). For 0% schema coverage, this is helpful, though more detail on how to obtain secure_filename would improve it.

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 'Create a time-limited public URL for a build artifact,' specifying the verb, resource, and key attribute (time-limited). This distinguishes it from sibling tools like get_artifact_url (which retrieves existing URLs) and other artifact-related tools.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites or limitations. For example, it does not mention that the artifact must exist first or that this complements get_artifact_url for retrieving an existing 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