Skip to main content
Glama

google_delete_image

Remove a specific uploaded image from a Google Play listing using package name, edit ID, language, image type, and image ID.

Instructions

Delete a specific uploaded image

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesAndroid package name
editIdYesEdit ID
languageYesLanguage code
imageTypeYesImage type
imageIdYesImage ID to delete

Implementation Reference

  • Handler definition for google_delete_image tool - calls GoogleClient.deleteImage() with packageName, editId, language, imageType, imageId
    const deleteImage: ToolDef = {
      name: 'google_delete_image',
      description: 'Delete a specific uploaded image',
      schema: z.object({
        packageName: z.string().describe('Android package name'),
        editId: z.string().describe('Edit ID'),
        language: z.string().describe('Language code'),
        imageType: z.string().describe('Image type'),
        imageId: z.string().describe('Image ID to delete'),
      }),
      handler: async (client, args) => {
        await client.deleteImage(
          args.packageName, args.editId, args.language, args.imageType, args.imageId,
        );
        return { success: true };
      },
    };
  • Input schema for google_delete_image - requires packageName, editId, language, imageType, imageId
    schema: z.object({
      packageName: z.string().describe('Android package name'),
      editId: z.string().describe('Edit ID'),
      language: z.string().describe('Language code'),
      imageType: z.string().describe('Image type'),
      imageId: z.string().describe('Image ID to delete'),
    }),
  • src/index.ts:76-92 (registration)
    Registration loop for all Google tools including google_delete_image via MCP 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 };
        }
      });
    }
  • GoogleClient.deleteImage() - calls the Google Play Android Publisher API edits.images.delete endpoint
    async deleteImage(
      packageName: string,
      editId: string,
      language: string,
      imageType: string,
      imageId: string,
    ) {
      await this.publisher.edits.images.delete({
        packageName, editId, language, imageType, imageId,
      });
    }
  • Export array of all Google tools including deleteImage (google_delete_image)
    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,
Behavior2/5

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

With no annotations, the description carries the full burden. It fails to disclose any behavioral traits such as idempotency, permission requirements, or whether the deletion is irreversible.

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?

Very concise single phrase, front-loaded with the verb. However, it lacks any structure beyond a bare statement.

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 5 required parameters tied to a complex edit workflow, the description provides no context about the edit lifecycle or what happens on success (e.g., success response). Agents lack critical workflow information.

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%, so baseline is 3. Description adds no additional meaning beyond the schema's parameter descriptions, which are adequate.

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?

Description clearly specifies action ('Delete') and resource ('a specific uploaded image'), distinguishing it from sibling tools like google_delete_all_images.

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 guidance on when to use this tool versus alternatives, nor any context about required prerequisites (e.g., needing an active edit from google_create_edit).

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