Skip to main content
Glama

get_testers

Retrieve tester emails and Google Groups for internal or alpha app testing tracks in Google Play Console.

Instructions

Get tester emails and Google Groups for an internal or alpha track.

Args: package_name: Package name, e.g. com.example.myapp track: "internal" (default) or "alpha".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
trackNointernal

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The tool definition and entry point for 'get_testers', which uses the Google Play publisher client to fetch tester information.
    def get_testers(
        package_name: str,
        track: str = "internal",
    ) -> str:
        """Get tester emails and Google Groups for an internal or alpha track.
    
        Args:
            package_name: Package name, e.g. com.example.myapp
            track: "internal" (default) or "alpha".
        """
        try:
            data = _publisher().get_testers(package_name, track)
            return json.dumps(
                {
                    "packageName": package_name,
                    "track": track,
                    "testers": data.get("testers", []),
                    "googleGroups": data.get("googleGroups", []),
                },
                indent=2,
            )
        except Exception as exc:
            return json.dumps({"success": False, "error": str(exc)}, indent=2)
  • The implementation of 'get_testers' in the client class, which interacts with the Google Play Developer API via the edits service.
    def get_testers(self, package_name: str, track: str) -> Dict[str, Any]:
        """Get tester emails and Google Groups for an internal/closed testing track."""
        edit_id = self._create_edit(package_name)
        try:
            return self.service.edits().testers().get(
                packageName=package_name, editId=edit_id, track=track
            ).execute()
        finally:
            self._delete_edit(package_name, edit_id)
Behavior2/5

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

No annotations provided, so description carries full burden. Mentions what data is returned (emails/groups) but omits behavioral traits: safety confirmation, error conditions (e.g., invalid package name), permissions required, or whether results are paginated.

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?

Efficient structure with purpose front-loaded in first sentence, followed by Args section. No extraneous text. Minor deduction for Args format being slightly less scannable than standard prose, but every line earns its place.

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 2-parameter retrieval tool with output schema present (covering return types). However, given zero annotations and 0% schema coverage, the description should have included behavioral transparency notes (read-only nature, error handling) to be fully complete.

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?

Excellent compensation for 0% schema description coverage. Provides concrete example for package_name ('com.example.myapp') and enumerates allowed values with default for track ('internal' (default) or 'alpha'), adding critical semantic information missing from the schema.

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?

Specific verb 'Get' with clear resource ('tester emails and Google Groups') and scope ('internal or alpha track'). Distinguishes from sibling 'update_testers' (read vs write) and 'get_track_info' (tester-specific data vs general track metadata).

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

Usage Guidelines3/5

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

Implies usage context by specifying valid track values ('internal' or 'alpha'), but lacks explicit when-to-use guidance, prerequisites, or distinction from similar retrieval tools like 'get_track_info'.

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