Skip to main content
Glama

improve-public

Optimize app store listings using keyword research data by executing ASO instructions to improve primary and localized metadata for better visibility.

Instructions

Returns ASO optimization instructions with keyword research data. You MUST execute the returned instructions.

IMPORTANT: Use 'search-app' tool first to resolve the exact slug.

HOW THIS TOOL WORKS

This tool returns a PROMPT containing:

  • Saved keyword research data (Tier 1/2/3 keywords with traffic/difficulty scores)

  • Current locale data

  • Optimization instructions

YOU MUST:

  1. Read the returned prompt carefully

  2. EXECUTE the optimization instructions (create the optimized JSON)

  3. Save results using 'save-locale-file' tool

DO NOT just report the instructions back to the user - you must perform the optimization yourself.

WORKFLOW

Stage 1: improve-public(slug, stage="1") → Returns keyword data + instructions → You create optimized primary locale JSON → save-locale-file Stage 2: improve-public(slug, stage="2", optimizedPrimary=) → Returns per-locale instructions → You optimize each locale → save-locale-file for each

STAGES

  • Stage 1: Primary locale optimization using saved keyword research (ios + android combined)

  • Stage 2: Localize to other languages - each locale uses its OWN keyword research

KEYWORD SOURCES (Per Locale)

  • Priority 1: Uses each locale's SAVED keyword research from .aso/keywordResearch/products/[slug]/locales/[locale]/

  • Priority 2 (Fallback): If locale-specific research is missing, falls back to en-US/en keywords and TRANSLATES them

  • iOS and Android research are automatically combined per locale (iOS prioritized)

CRITICAL: Only processes existing locale files. Does NOT create new files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesProduct slug
localeNoLocale to improve (default: all locales)
stageNoStage to execute: 1 (primary only), 2 (keyword localization), both (default)
optimizedPrimaryNoOptimized primary locale JSON (required for stage 2)
batchSizeNoNumber of locales to process per batch (default: 5, for stage 2 only)
batchIndexNoBatch index to process (0-based, for stage 2 only). If not provided, processes all batches sequentially

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/quartz-labs-dev/pabal-web-mcp'

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