Skip to main content
Glama

upload_to_internal_sharing

Upload APK or AAB files to Google Play Console's Internal App Sharing to generate shareable testing links for quick one-off app testing.

Instructions

Upload APK or AAB to Internal App Sharing and get a shareable link.

Shares a build via URL without assigning it to a track. Ideal for quick one-off testing. File type auto-detected from extension (.apk/.aab).

Args: package_name: Package name, e.g. com.example.myapp file_path: Absolute local path to the APK or AAB.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
file_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual implementation of the upload_to_internal_sharing tool in the PublisherClient class.
    def upload_to_internal_sharing(
        self,
        package_name: str,
        file_path: str,
    ) -> Dict[str, Any]:
        """Upload an APK or AAB to Internal App Sharing.
    
        Returns a shareable download URL. Does NOT assign the build to any
        track — use this for quick tester distribution without a Play track.
        File type is inferred from the extension (.apk or .aab).
        """
        ext = os.path.splitext(file_path)[1].lower()
        if ext == ".apk":
            mime = APK_MIME
            artifact_type = "apk"
        elif ext == ".aab":
            mime = BUNDLE_MIME
            artifact_type = "bundle"
        else:
            raise ValueError(f"Unrecognized file extension '{ext}'. Use .apk or .aab.")
    
        media = MediaFileUpload(file_path, mimetype=mime, resumable=False)
        if artifact_type == "apk":
            result = self.service.internalappsharingartifacts().uploadapk(
                packageName=package_name, media_body=media
            ).execute()
        else:
            result = self.service.internalappsharingartifacts().uploadbundle(
                packageName=package_name, media_body=media
            ).execute()
        result["artifactType"] = artifact_type
        return result
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. Adds valuable behavioral details: file type auto-detection from extension and shareable link output. Missing: auth requirements, rate limits, file size constraints, expiration of links, or error conditions.

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?

Front-loaded with core purpose. 'Args:' format slightly unconventional but efficiently organizes parameter docs. Every sentence earns its place including the auto-detection detail. Could be tighter by integrating Args into prose.

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?

Appropriately complete given has output schema. Mentions expected output (shareable link) and covers both undocumented parameters. For a state-mutating upload with no safety annotations, could mention prerequisite permissions, but parameter coverage is solid.

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 titles). Description fully compensates by providing types/examples for both params: package_name format ('com.example.myapp') and file_path constraints ('Absolute local path'). Deducted one point for lacking validation rules or format constraints.

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?

Excellent specific verb+resource combination ('Upload APK or AAB to Internal App Sharing'). Explicitly distinguishes from track-based siblings via 'without assigning it to a track' and scopes use case to 'quick one-off testing' vs formal releases.

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?

Provides clear usage context ('Ideal for quick one-off testing') and implies workflow distinction from track-based tools. Lacks explicit sibling naming (e.g., 'unlike upload_artifact') or 'when not to use' exclusions.

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