Skip to main content
Glama

google_update_testers

Replace tester Google Groups assigned to a specific track in Google Play Console. Provide package name, edit ID, track name, and optional group emails to update.

Instructions

Update tester Google Groups for a track

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesAndroid package name
editIdYesEdit ID
trackYesTrack name (e.g. internal, alpha, beta)
googleGroupsNoList of Google Group email addresses

Implementation Reference

  • Tool definition for 'google_update_testers' containing the handler that delegates to GoogleClient.updateTesters()
    const updateTesters: ToolDef = {
      name: 'google_update_testers',
      description: 'Update tester Google Groups for a track',
      schema: z.object({
        packageName: z.string().describe('Android package name'),
        editId: z.string().describe('Edit ID'),
        track: z.string().describe('Track name (e.g. internal, alpha, beta)'),
        googleGroups: z.array(z.string()).optional().describe('List of Google Group email addresses'),
      }),
      handler: async (client, args) => {
        const { packageName, editId, track, ...testers } = args;
        return client.updateTesters(packageName, editId, track, testers);
      },
    };
  • Zod schema defining the input parameters: packageName, editId, track, and optional googleGroups array
    schema: z.object({
      packageName: z.string().describe('Android package name'),
      editId: z.string().describe('Edit ID'),
      track: z.string().describe('Track name (e.g. internal, alpha, beta)'),
      googleGroups: z.array(z.string()).optional().describe('List of Google Group email addresses'),
    }),
  • Tool registration in the exported googleTools array, which is iterated over in src/index.ts to register with the MCP server
    export const googleTools: ToolDef[] = [
      // Edit lifecycle
      createEdit, commitEdit, validateEdit, deleteEdit,
      // App details
      getDetails, updateDetails,
      // Store listing
      listListings, getListing, updateListing, deleteListing,
      // Country availability & Testers
      getCountryAvailability, getTesters, updateTesters,
      // Images
      listImages, uploadImage, deleteImage, deleteAllImages,
      // Tracks & Releases
      listTracks, getTrack, createRelease, promoteRelease, haltRelease,
      // Bundle / APK
      uploadBundle, uploadApk,
      // Reviews
      listReviews, getReview, replyToReview,
      // In-App Products
      listInAppProducts, getInAppProduct, createInAppProduct, updateInAppProduct, deleteInAppProduct,
      // Subscriptions
      listSubscriptions, getSubscription, archiveSubscription,
    ];
  • GoogleClient.updateTesters() method that calls the Google Play Android Publisher API edits.testers.patch to update tester groups
    async updateTesters(
      packageName: string,
      editId: string,
      track: string,
      testers: { googleGroups?: string[] },
    ) {
      const res = await this.publisher.edits.testers.patch({
        packageName, editId, track,
        requestBody: testers,
      });
      return res.data;
    }
  • src/index.ts:77-92 (registration)
    MCP server registration loop that registers all googleTools (including google_update_testers) with the MCP server
    for (const tool of googleTools) {
      server.tool(tool.name, tool.description, tool.schema.shape, async (args: any) => {
        if (!googleClient) {
          return {
            content: [{ type: 'text' as const, text: 'Google client not configured. Set GOOGLE_SERVICE_ACCOUNT_PATH env var.' }],
            isError: true,
          };
        }
        try {
          const result = await tool.handler(googleClient, args);
          return { content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }] };
        } catch (err: any) {
          return { content: [{ type: 'text' as const, text: `Error: ${err.message}` }], isError: true };
        }
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Update', implying mutation, but lacks details on permissions, side effects, or consequences (e.g., whether changes are immediate, require a commit, etc.).

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?

The description is a single, concise sentence with no superfluous words. It is front-loaded with the action. However, it could be slightly more informative without sacrificing brevity.

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?

For a mutation tool with no output schema and no annotations, the description is too minimal. It does not explain what happens when testers are updated (e.g., replaces or appends), or the need to commit edits. The high schema coverage partially compensates, but completeness is lacking.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema fully documents all parameters. The description adds no additional meaning beyond the schema, meeting the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update') and the resource ('tester Google Groups for a track'). However, it does not differentiate from sibling tools like 'google_get_testers' or other update tools, but the verb and resource are specific enough.

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 (e.g., when to use google_get_testers or other Google tools). No exclusions or context are given.

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/mikusnuz/app-publish-mcp'

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