Prepare In-App Event Copy
prepare_iaeCreate App Store In-App Event (IAE) copy briefs with character-limited variations from supplied keywords, event purpose, and locale. Outputs structured report for event metadata.
Instructions
Prepare an iOS App Store In-App Event (IAE) — generate copy variations and a final report.
Use this when the user wants to create or draft an in-app event, prepare IAE metadata, or generate App Store event copy. Accepts user-supplied keywords and event parameters, then returns a structured brief. Do not use it for ordinary App Store listing metadata (title, subtitle, description) — it covers In-App Event fields only.
Runs entirely locally: no network calls, no App Store or SensorTower lookup, and no keyword research of its own — the caller supplies the keywords (reach for research_rivals or search_app_store first if you still need to find them). Returns immediately.
After receiving the tool output, you MUST:
Generate 3 distinct copy variations in the target language (from
locale.language), each differing meaningfully in angle, tone, or keyword emphasis. For each variation produce:Event name (hard limit: 30 chars — count every character; trim at word boundary if over)
Short description (hard limit: 50 chars — same rules)
Long description (hard limit: 120 chars — same rules) Display every field with its exact character count and ✓ / ✗ indicator. Fix any ✗ before showing the user. Keyword placement: Tier 1 keywords must appear in short description and long description; embed in event name only if it fits naturally. Prioritize keywords toward the beginning of each field. Copy rules: active voice, present tense, no pricing claims or % discounts, no competitor names, all three fields independently meaningful. If locale is not en-US, add an English translation line under each localized field so the user can verify meaning.
Ask the user to choose one variation.
After the user picks a variation, print the output table and the final summary report using this exact format:
Output table:
CHOSEN VARIATION — <locale.appleCode>
─────────────────────────────────────
Event name : <text> (<N>/30)
Short description : <text> (<N>/50)
Long description : <text> (<N>/120)
─────────────────────────────────────
Next step: upload event artwork in App Store Connect
• Event card image : 2160 × 1080 px
• App icon overlay : 1024 × 1024 pxFinal summary report:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
IN-APP EVENT REPORT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
IAE locale : <locale.appleCode> (<locale.language> — <locale.country>)
Keyword store : <locale.store> store
Target audience : <audience>
Event context : <event_context>
Goal : <goal>
Tone : <tone>
─────────────────────────────────────
Keywords used : <Tier 1 placed> | <Tier 2 placed>
Event name : <text> (<N>/30 chars)
Short description: <text> (<N>/50 chars)
Long description : <text> (<N>/120 chars)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CHECKLIST
[ ] IAE locale is <locale.appleCode>
[ ] Event name ≤ 30 chars
[ ] Short description ≤ 50 chars
[ ] Long description ≤ 120 chars
[ ] No pricing claims or % discounts
[ ] No competitor names
[ ] Event artwork assets prepared (1024×1024 + 2160×1080)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Flag any checklist item that is not yet satisfied.
Returns JSON with the structured brief for generating copy.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | Primary conversion goal (e.g. increase conversions, attract new users, boost engagement). | |
| tone | Yes | Copy tone. | |
| locale | Yes | Target locale/language for the IAE copy (e.g. en-us, en-gb, de-de, fr-fr, tr, ja, ko, zh-hans). An unlisted value returns an `unknown_locale` error naming the supported ones. | |
| audience | Yes | Target audience (e.g. students, professionals, parents, casual users). | |
| keywords | Yes | Ordered list of keywords by priority (index 0–2 = Tier 1 must-use, 3–6 = Tier 2, 7–9 = Tier 3). Maximum 10. | |
| event_context | Yes | Real-world hook tying the event to a moment (e.g. a holiday, season, product milestone). | |
| event_purpose | Yes | 1–2 sentences describing what the event is about and why users should care. |