Skip to main content
Glama

google_update_details

Update Google Play app listing details for a given edit: set default language, support email, phone, and website.

Instructions

Update app details (default language, contact email/phone/website)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesAndroid package name
editIdYesEdit ID
defaultLanguageNoDefault language code in BCP 47 format (e.g. en-US)
contactWebsiteNoUser-visible website URL
contactEmailNoUser-visible support email
contactPhoneNoUser-visible support phone number

Implementation Reference

  • The tool definition and handler for 'google_update_details'. It extracts packageName/editId and passes remaining details to client.updateDetails.
    const updateDetails: ToolDef = {
      name: 'google_update_details',
      description: 'Update app details (default language, contact email/phone/website)',
      schema: z.object({
        packageName: z.string().describe('Android package name'),
        editId: z.string().describe('Edit ID'),
        defaultLanguage: z.string().optional().describe('Default language code in BCP 47 format (e.g. en-US)'),
        contactWebsite: z.string().optional().describe('User-visible website URL'),
        contactEmail: z.string().optional().describe('User-visible support email'),
        contactPhone: z.string().optional().describe('User-visible support phone number'),
      }),
      handler: async (client, args) => {
        const { packageName, editId, ...details } = args;
        return client.updateDetails(packageName, editId, details);
      },
    };
  • Zod schema defining the input parameters for google_update_details: packageName, editId, and optional fields defaultLanguage, contactWebsite, contactEmail, contactPhone.
    schema: z.object({
      packageName: z.string().describe('Android package name'),
      editId: z.string().describe('Edit ID'),
      defaultLanguage: z.string().optional().describe('Default language code in BCP 47 format (e.g. en-US)'),
      contactWebsite: z.string().optional().describe('User-visible website URL'),
      contactEmail: z.string().optional().describe('User-visible support email'),
      contactPhone: z.string().optional().describe('User-visible support phone number'),
    }),
  • updateDetails is included in the googleTools export array, which is then registered as an MCP tool in src/index.ts line 77-92 via server.tool().
    getDetails, updateDetails,
  • The GoogleClient.updateDetails() method that calls the Google Play Android Publisher API edits.details.patch() endpoint to update app details.
    async updateDetails(
      packageName: string,
      editId: string,
      details: { defaultLanguage?: string; contactWebsite?: string; contactEmail?: string; contactPhone?: string },
    ) {
      const res = await this.publisher.edits.details.patch({
        packageName, editId,
        requestBody: details,
      });
      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 bears full burden. It only says 'Update' implying mutation, but does not disclose requirements (permissions, edit ID management), reversibility, or side effects on unchanged fields.

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 very short and front-loaded, containing no unnecessary words. However, it could be slightly more informative without sacrificing conciseness.

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 is part of an edit workflow with 6 parameters and no output schema, the description lacks critical context about the required editId lifecycle and that changes are not committed until google_commit_edit is called.

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 coverage is 100% with clear parameter descriptions. The description repeats the field names but does not add deeper semantics beyond grouping them as 'app details'. Baseline 3 is appropriate.

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 tool updates app details and lists specific fields (default language, contact email/phone/website). It distinguishes from sibling tools like google_update_listing which update store listing details.

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?

No when-to-use or when-not-to-use guidance is provided. The description does not mention that an edit must be created first and changes committed later, nor does it contrast with similar update tools like google_update_listing.

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