---
name: read-the-ad-back
description: Use after a paid ad launches, or when asked to verify live ads, creatives, CTAs, or destination URLs. Pulls each ad from the ad platform itself and compares it to the approved plan, flagging mismatches.
---

# Read the ad back

What you approved and what actually shipped are not always the same. After launch, pull each ad from the platform itself and check it.

## Instructions

1. **Read from the platform, not from memory.** Fetch the live ad objects (creative, CTA, destination URL, status, and targeting) using the ads API or MCP available in this session. Do not assume the draft you wrote earlier is what shipped.
2. **Compare to the approved plan.** For each live ad, list:
   - Creative (copy, image or video asset)
   - CTA
   - Destination URL
   - And whether each matches the approved plan
3. **Flag mismatches clearly.** If anything differs, highlight it and recommend a fix. Do not silently overwrite live ads.
4. **Do not keep spending on a mismatch.** Call out the issue before more budget goes out, and wait for the human to decide whether to pause, fix, or accept the change.

## Optional: Synter MCP

If Synter MCP is connected, use `get_ad_readback` to pull live ads. It supports Meta, Reddit, LinkedIn, and Google Ads. For other platforms, use that platform's native ads API or MCP the same way.