Skip to main content
App Store metadata, screenshots, and localization Level: Intermediate 11 min read

Deleting App Store Screenshots Safely via MCP Tooling

A complete developer guide to safely identifying, previewing, and deleting outdated App Store screenshots via FlightDeck operation staging without accidental asset loss.

Published: 2026-11-02 • Last Updated: 2026-11-02 • Author: Kip Lawrence
Key MCP Tools: app_screenshots_listflightdeck_operation_stagerelease_readiness_check

Overview: The Irreversibility of Screenshot Deletion

As your application evolves, older marketing screenshots showing outdated UI layouts, superseded features, or obsolete OS designs must be retired. However, deleting screenshots in App Store Connect requires extreme caution:

  1. Deletion is Permanent and Irreversible: Once a screenshot asset is deleted via Apple's API or web portal, Apple immediately unlinks and purges the binary image from its edge CDN. It cannot be "undone" or restored from a trash bin. If you delete the wrong asset, you must locate the original master file and perform a complete re-upload.
  2. Multi-Locale Complexity: Large applications maintain screenshots across 20+ localized storefronts and multiple device display tiers (e.g., iPhone 6.9-inch, 6.7-inch, 6.5-inch, and iPad 13-inch). Identifying the exact target asset requires isolating the correct locale, display family, and position.
  3. Minimum Storefront Thresholds: Apple strictly mandates that every supported device family contain at least one valid screenshot. Deleting the sole screenshot in an iPhone set creates an immediate BLOCKER under App Store Review Guideline 2.1 (App Completeness).
  4. Version State Boundaries: Screenshots are permanently locked on approved live releases (READY_FOR_SALE). You can only delete screenshots from an active, editable version draft.

Using FlightDeck with an AI coding assistant, you can implement a safe, multi-step verification protocol to preview, stage, and delete screenshots with human-in-the-loop protection.

TEXT
┌────────────────────────────────────────────────────────────────────────┐
│                   SCREENSHOT DELETION SAFETY PIPELINE                  │
│                                                                        │
│   1. Inspect Draft State  ──► Confirm Version is PREPARE_FOR_SUBMISSION│
│   2. Query Target Set     ──► [ app_screenshots_list ]                 │
│   3. Identify Exact Asset ──► Filter by Locale, Display Type, Position │
│   4. Save Local Backup    ──► Confirm master copy stored locally       │
│   5. Check Thresholds     ──► Confirm remaining count >= 1             │
│   6. Preview in Chat      ──► Assistant shows Target ID, Size, Preview │
│   7. User Confirmation    ──► Developer gives explicit in-chat approval│
│   8. Desktop Approval     ──► Human Inspects Diff & Clicks [Approve]   │
│   9. Direct Apple API     ──► DELETE /v1/appScreenshots/{id} (TLS)     │
│  10. Readback & Verify    ──► Confirm Remaining Order & Readiness PASS │
└────────────────────────────────────────────────────────────────────────┘
Important

FlightDeck MCP Operational Architecture: FlightDeck does not expose a bespoke semantic tool named app_screenshot_delete. Deleting a screenshot programmatically is performed using FlightDeck's Universal Operation Dispatcher (flightdeck_operation_stage) targeting Apple's official endpoint appScreenshots_deleteInstance (DELETE /v1/appScreenshots/{id}).

Alternatively, developers can delete screenshots manually in the App Store Connect web portal by hovering over the target image and clicking the red delete icon. Any programmatic deletion staged via FlightDeck requires physical approval in the Desktop Approval Center.


Quick Answer: The 7-Step Safe Deletion Sequence

To safely delete an App Store screenshot without risking data loss or submission rejections, always follow this 7-step sequence:

  1. Inspect Screenshot Details: Query app_screenshots_list to fetch the authoritative list of screenshot IDs, file names, and dimensions.
  2. Verify Target Hierarchy: Confirm the exact application ID, version draft, locale code (e.g. en-US), and display family (e.g. APP_IPHONE_69).
  3. Save a Local Backup: Verify that a copy of the screenshot exists on your local disk or repository before issuing the deletion.
  4. Preview Deletion in Chat: Require the AI assistant to display a preview showing the target image details and the remaining screenshot count (verifying remaining count >= 1).
  5. Give Explicit User Confirmation: Confirm in chat that you approve staging the deletion.
  6. Physical Desktop Approval: Inspect the deletion card in FlightDeck Desktop's Approval Center and click Approve.
  7. Post-Deletion Readback: Query app_screenshots_list and run release_readiness_check to verify that the remaining set satisfies Apple submission rules.

Copyable Prompts for Your AI Coding Assistant

1. Discover and Preview Screenshots Before Deletion

Use this prompt to find the exact screenshot you want to delete without manually searching for opaque Apple resource IDs:

MARKDOWN
Please inspect our active App Store Connect draft version using FlightDeck:
1. List all screenshots configured for our English (U.S.) iPhone 6.9-inch display set.
2. Present a table showing:
   - Position (1, 2, 3...)
   - Screenshot ID
   - File Name / Original Upload Name
   - Pixel Dimensions
   - Total count in this set
3. Tell me which screenshot corresponds to position 4 ("Settings and Customization").
4. Do not delete anything yet—wait for my confirmation.

2. Stage Safe Screenshot Deletion

Once you have identified the screenshot to remove:

MARKDOWN
We need to remove screenshot position 4 from our English (U.S.) iPhone 6.9-inch display set:
1. Confirm that removing this screenshot will leave at least 1 valid screenshot in the set.
2. Display a confirmation preview showing the target screenshot details and remaining count.
3. Once I review the preview, stage the deletion in FlightDeck for my review in the Desktop Approval Center.
4. Do not execute or commit without my desktop confirmation.

3. Readback Verification and Submission Readiness

After approving the deletion in FlightDeck Desktop:

MARKDOWN
Please perform an authoritative readback using FlightDeck:
1. List the remaining screenshots in our English (U.S.) iPhone 6.9-inch set to confirm the target screenshot was removed.
2. Check release readiness on our draft version to ensure no "Missing Screenshots" blockers were introduced.
3. Report the updated screenshot count and submission readiness status.

The 10-Point Safe Deletion Checklist

Before executing any screenshot deletion, verify that every item on this checklist is satisfied:

Step Verification Check Validation Standard Failure Mode
1 Target App Match target appId in FlightDeck. Accidental deletion on wrong application record.
2 Version State Version must be PREPARE_FOR_SUBMISSION or DEVELOPER_REJECTED. API error 409 Conflict if version is live or in review.
3 Locale Isolation Verify locale code (e.g., en-US vs es-ES). Deleting global English screenshot instead of localized translation.
4 Display Family Verify display enum (e.g., APP_IPHONE_69). Deleting 6.9" iPhone screenshot instead of iPad asset.
5 Position Match Confirm visual content matches intended asset. Deleting the primary hero screenshot by mistake.
6 Minimum Count Remaining screenshots in set must be >= 1. Rejection under Guideline 2.1 for empty screenshot set.
7 Master Backup Confirm original PNG exists in local Git/archive. Irreversible loss of creative marketing artwork.
8 Approval Review Review payload in Desktop Approval Center. Accidental programmatic execution by autonomous scripts.
9 Readback Check Authoritative GET confirms asset purged. Ghost assets remaining in cache.
10 Readiness Audit release_readiness_check returns 0 blockers. Submission blocked at review gate.

Technical Deletion Workflow: Web Portal vs. MCP Dispatcher

MERMAID
graph TD
    A[Start: Delete Outdated Screenshot] --> B{Choose Workflow}
    
    B -->|Visual / Portal| C[App Store Connect Web Portal]
    C --> C1[Open App > Version Draft]
    C1 --> C2[Scroll to Screenshots Section]
    C2 --> C3[Hover over target image]
    C3 --> C4[Click red Delete icon]
    C4 --> C5[Click Save]
    
    B -->|Scripted / AI Assisted| D[FlightDeck MCP Universal Dispatcher]
    D --> D1[Assistant queries screenshots via app_screenshots_list]
    D1 --> D2[Assistant isolates target screenshotId]
    D2 --> D3[Assistant stages appScreenshots_deleteInstance]
    D3 --> D4[Desktop Approval Center surfaces confirmation card]
    D4 --> D5[Human developer reviews diff & clicks Approve]
    D5 --> D6[Direct DELETE to Apple API over TLS 1.3]
    
    C5 --> E[Apple permanently purges asset from CDN]
    D6 --> E
    E --> F[Run release_readiness_check]
    F --> G[Submission Readiness Confirmed]

Option A: App Store Connect Web Portal (Visual)

  1. Sign in to App Store Connect.
  2. Navigate to Apps > [Your App] > iOS App [Draft Version].
  3. Under Screenshots, select the target display size tab (e.g., 6.9" Display).
  4. Hover your mouse over the screenshot you wish to remove.
  5. Click the red minus/delete icon in the top-right corner of the thumbnail.
  6. Click Save in the top-right corner.

Option B: FlightDeck Universal Operation Dispatcher (Programmatic)

For developers managing releases through AI coding assistants:

JSON
{
  "operationId": "appScreenshots_deleteInstance",
  "pathParameters": {
    "id": "scr_old_dashboard_987654"
  }
}

In FlightDeck Desktop, the Approval Center intercepts the mutation and requires human confirmation before issuing the DELETE HTTP request.


Authoritative Readback Verification

After deleting a screenshot, always verify that the remaining set satisfies Apple's constraints:

MARKDOWN
Run a verification audit on our draft version using FlightDeck:
1. Inspect our screenshot sets for the English (U.S.) iPhone 6.9-inch display.
2. Confirm that the deleted screenshot ID is no longer present.
3. Check release readiness to verify that the screenshot set is valid and submittable.

FlightDeck returns the verified state:

TEXT
Screenshot Set: APP_IPHONE_69 (English U.S.)
Total Screenshots: 3 / 10
Blockers: 0
Warnings: 0
Submission Readiness: READY_FOR_SUBMISSION

Troubleshooting Common Deletion Errors

1. "Screenshots cannot be modified on approved versions"

  • Cause: Attempting to delete a screenshot when the version is in READY_FOR_SALE state.
  • Fix: Live versions are immutable. You must create a new version draft (app_store_version_create) to modify marketing assets.

2. "A minimum of one screenshot is required for this display type"

  • Cause: Deleting the only screenshot in an active display set.
  • Fix: If you want to replace the image, upload the new screenshot first using app_screenshot_upload_plan, then delete the old one. Never leave an active display set empty.

3. "The requested resource could not be found"

  • Cause: The screenshot was already deleted in another session or the ID was mistyped.
  • Fix: Run app_screenshots_list to fetch the authoritative list of current screenshot IDs.

Security & Verification Safeguards

  • Multi-Factor Approval: Programmatic deletions cannot bypass FlightDeck Desktop's mandatory physical human confirmation.
  • Zero Intermediary Cloud: All deletion requests travel directly between your Mac and Apple's secure API servers over TLS 1.3.
  • Audit Logging: Every deletion is permanently recorded in FlightDeck's local audit trail with cryptographic timestamps and operator signatures.

Official Apple Documentation

Connect Your AI Agent to App Store Connect

FlightDeck runs locally on your Mac, keeping private keys secure in your macOS Keychain and executing mutations only after your explicit approval.

Download FlightDeck on Mac App Store