Skip to main content
Glama

google_create_release

Create a release on Android tracks (internal, alpha, beta, production) with version codes, release notes, status, and staged rollout fraction for production.

Instructions

Create a release on a track with optional version codes and release notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesAndroid package name
editIdYesEdit ID
trackYesTarget track
versionCodesNoVersion codes to include
releaseNotesNoRelease notes per language
statusNocompleted
userFractionNoStaged rollout fraction (0.0-1.0, only for production)
releaseNameNoRelease name/label

Implementation Reference

  • The 'google_create_release' tool definition — builds a release object from args and calls client.updateTrack. This is the main handler function.
    const createRelease: ToolDef = {
      name: 'google_create_release',
      description: 'Create a release on a track with optional version codes and release notes',
      schema: z.object({
        packageName: z.string().describe('Android package name'),
        editId: z.string().describe('Edit ID'),
        track: z.enum(['internal', 'alpha', 'beta', 'production']).describe('Target track'),
        versionCodes: z.array(z.string()).optional().describe('Version codes to include'),
        releaseNotes: z.array(z.object({
          language: z.string(),
          text: z.string(),
        })).optional().describe('Release notes per language'),
        status: z.enum(['draft', 'halted', 'completed', 'inProgress']).default('completed'),
        userFraction: z.number().optional().describe('Staged rollout fraction (0.0-1.0, only for production)'),
        releaseName: z.string().optional().describe('Release name/label'),
      }),
      handler: async (client, args) => {
        const release: any = {
          status: args.status,
        };
        if (args.versionCodes) release.versionCodes = args.versionCodes;
        if (args.releaseNotes) release.releaseNotes = args.releaseNotes;
        if (args.userFraction) release.userFraction = args.userFraction;
        if (args.releaseName) release.name = args.releaseName;
    
        return client.updateTrack(args.packageName, args.editId, args.track, [release]);
      },
  • Zod schema defining the input validation for google_create_release — requires packageName, editId, track; optional versionCodes, releaseNotes, status, userFraction, releaseName.
    schema: z.object({
      packageName: z.string().describe('Android package name'),
      editId: z.string().describe('Edit ID'),
      track: z.enum(['internal', 'alpha', 'beta', 'production']).describe('Target track'),
      versionCodes: z.array(z.string()).optional().describe('Version codes to include'),
      releaseNotes: z.array(z.object({
        language: z.string(),
        text: z.string(),
      })).optional().describe('Release notes per language'),
      status: z.enum(['draft', 'halted', 'completed', 'inProgress']).default('completed'),
      userFraction: z.number().optional().describe('Staged rollout fraction (0.0-1.0, only for production)'),
      releaseName: z.string().optional().describe('Release name/label'),
    }),
  • The createRelease tool is exported in the googleTools array, which is iterated over in src/index.ts to register each tool 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,
  • src/index.ts:76-92 (registration)
    The loop that registers all google tools (including google_create_release) with the MCP server via server.tool().
    // ── Register Google tools ──
    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 };
        }
      });
    }
  • The GoogleClient.updateTrack method that actually calls the Google Play Android Publisher API to persist the release.
    async updateTrack(
      packageName: string,
      editId: string,
      track: string,
      releases: androidpublisher_v3.Schema$TrackRelease[],
    ) {
      const res = await this.publisher.edits.tracks.update({
        packageName, editId, track,
        requestBody: { track, releases },
      });
      return res.data;
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behaviors, but it only states the basic action. It does not mention that this is a write operation, that it modifies an edit session requiring subsequent commit, or side effects like replacing an existing release on the track. The status and userFraction fields imply staged rollout behavior but are not explained.

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 concise (single sentence) and directly communicates the main action. It is efficient but could benefit from slight elaboration on key options.

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?

Given the tool's complexity (8 parameters, no output schema, no annotations), the description is insufficient. It omits critical context: that this operates within a Google Play Edit, that an edit must be created first via google_create_edit, that the release becomes active only after committing, and what the return value is. The high number of parameters and absence of output schema increase the need for completeness.

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 high (88%), so the baseline is 3. The description adds minimal value beyond labeling versionCodes and releaseNotes as 'optional', which is already evident from the schema. No additional semantic clarity is provided.

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?

The description clearly states the action 'Create a release on a track' with optional parameters, accurately capturing the tool's purpose and distinguishing it from related tools like google_promote_release or google_halt_release.

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 lacks any guidance on when to use this tool versus alternatives, prerequisites (e.g., requiring an edit ID), or the step in the overall workflow. Sibling tools like google_promote_release share similar context but are not mentioned.

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