Skip to main content
Glama

list_artifacts

Retrieve uploaded APKs and AABs for a Google Play app to identify version codes and SHA hashes, enabling track assignment and release management.

Instructions

List all APKs and AABs uploaded to the app.

Returns version codes and SHA hashes. Useful for finding version codes available to assign to a track.

Args: package_name: Package name, e.g. com.example.myapp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler function for 'list_artifacts' which formats the data retrieved from the Google Play API.
    @mcp.tool()
    def list_artifacts(package_name: str) -> str:
        """List all APKs and AABs uploaded to the app.
    
        Returns version codes and SHA hashes. Useful for finding version codes
        available to assign to a track.
    
        Args:
            package_name: Package name, e.g. com.example.myapp
        """
        try:
            data = _publisher().list_artifacts(package_name)
            apks = [
                {
                    "type": "apk",
                    "versionCode": a.get("versionCode"),
                    "sha1": a.get("binary", {}).get("sha1"),
                    "sha256": a.get("binary", {}).get("sha256"),
                }
                for a in data.get("apks", [])
            ]
            bundles = [
                {
                    "type": "bundle",
                    "versionCode": b.get("versionCode"),
                    "sha256": b.get("sha256"),
                }
                for b in data.get("bundles", [])
            ]
            all_artifacts = sorted(
                apks + bundles,
                key=lambda x: x.get("versionCode") or 0,
                reverse=True,
            )
            return json.dumps(
                {
                    "packageName": package_name,
                    "totalCount": len(all_artifacts),
                    "artifacts": all_artifacts,
                },
                indent=2,
            )
  • The underlying client method that performs the API call to list artifacts from Google Play.
    def list_artifacts(self, package_name: str) -> Dict[str, Any]:
        """List all APKs and AABs currently known for the app."""
        edit_id = self._create_edit(package_name)
        try:
            apks = self.service.edits().apks().list(
                packageName=package_name, editId=edit_id
            ).execute().get("apks", [])
            bundles = self.service.edits().bundles().list(
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses return contents ('Returns version codes and SHA hashes') which is valuable since output schema exists. However, omits safety classification (read-only), authentication requirements, or pagination behavior typical of Google Play API list operations.

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?

Four efficient sections: operation definition, return values, use case context, and parameter documentation. Zero redundancy. Information is front-loaded (action and resource first). Args section follows standard docstring convention.

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

Completeness5/5

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

Given low complexity (1 parameter, no nested objects) and existence of output schema, description is appropriately complete. Covers purpose, return data semantics, usage context, and parameter identification without over-specifying what the output schema should define.

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': 'Package Name'). Description compensates by providing example format 'com.example.myapp' in Args section, clarifying expected input pattern. Does not fully explain constraints (e.g., must match Play Console app ID) but provides essential semantic context through the example.

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 uses specific verb 'List' with specific resources 'APKs and AABs' (Android artifacts). Clearly distinguishes from siblings: vs upload_artifact (creates), vs list_tracks (tracks vs binaries), vs create_release/promote_release (actions vs inventory). Scope is tightly defined to uploaded app binaries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states use case: 'Useful for finding version codes available to assign to a track.' This contextualizes when to invoke it (before track assignment operations) and links to track-related siblings. Lacks explicit 'when not to use' exclusions, but provides clear positive guidance.

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/GooglePlayConsoleMcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server