Skip to main content
Glama

update_testers

Replace tester lists for Google Play Console internal or alpha tracks. Use to manage access by updating email addresses and Google Groups for app testing.

Instructions

Replace the tester list for an internal or alpha track.

WARNING: Full replacement — omitted testers lose access. Call get_testers first to preserve existing testers.

Args: package_name: Package name, e.g. com.example.myapp track: "internal" (default) or "alpha". emails: Tester email addresses. Empty list removes all individuals. google_groups: Google Group addresses. Empty list removes all groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
trackNointernal
emailsNo
google_groupsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The server-side tool definition and handler for update_testers in the MCP server.
    @mcp.tool()
    def update_testers(
        package_name: str,
        track: str = "internal",
        emails: Optional[list[str]] = None,
        google_groups: Optional[list[str]] = None,
    ) -> str:
        """Replace the tester list for an internal or alpha track.
    
        WARNING: Full replacement — omitted testers lose access.
        Call get_testers first to preserve existing testers.
    
        Args:
            package_name: Package name, e.g. com.example.myapp
            track: "internal" (default) or "alpha".
            emails: Tester email addresses. Empty list removes all individuals.
            google_groups: Google Group addresses. Empty list removes all groups.
        """
        try:
            result = _publisher().update_testers(
                package_name=package_name,
                track=track,
                emails=emails,
                google_groups=google_groups,
  • The underlying implementation of the update_testers logic, interacting with the Google Play Developer API.
    def update_testers(
        self,
        package_name: str,
        track: str,
        emails: Optional[List[str]] = None,
        google_groups: Optional[List[str]] = None,
    ) -> Dict[str, Any]:
        """Replace the tester list for an internal/closed testing track.
    
        This is a full replacement — existing testers not in the new list
        will lose access.
        """
        body: Dict[str, Any] = {}
        if emails is not None:
            body["testers"] = emails
        if google_groups is not None:
            body["googleGroups"] = google_groups
    
        edit_id = self._create_edit(package_name)
        try:
            result = self.service.edits().testers().update(
                packageName=package_name, editId=edit_id, track=track, body=body
            ).execute()
            commit = self._commit_edit(package_name, edit_id)
            return {"testers": result, "commit": commit}
        except Exception:
            self._delete_edit(package_name, edit_id)
            raise
Behavior4/5

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

With no annotations provided, the description carries full burden of behavioral disclosure. It explicitly warns of the destructive replacement nature (omitted testers lose access), documents default values ('internal' default), and explains edge case behavior ('Empty list removes all'). Lacks only rate limit or permission details.

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?

Information-dense structure front-loads the critical warning before the Args section. The Args block is necessary given zero schema coverage, though slightly repetitive in format. Every sentence serves a safety or instructional purpose.

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?

Adequate for a destructive 4-parameter replacement operation. Since output schema exists, the description appropriately omits return value details while covering prerequisite workflows and destructive behavior warnings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage (titles only). The description fully compensates by documenting all 4 parameters: package_name includes example format, track specifies allowed values and default, and both list parameters explain empty-list semantics.

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?

Specifies exact operation ('Replace'), resource ('tester list'), and scope ('internal or alpha track'). Clearly distinguishes from sibling 'get_testers' by describing a destructive write operation versus a read operation.

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

Usage Guidelines5/5

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

Provides explicit prerequisite workflow ('Call get_testers first to preserve existing testers') and safety warning ('Full replacement — omitted testers lose access'). Clearly states when-not-to-use-blindly and references the correct sibling tool for the prerequisite step.

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