AgriciDaniel/claude-ads / ads
ads
VerifiedOperate professional paid advertising across Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, Apple, Amazon, Reddit, Pinterest, Snapchat, and X. Use for account intake, source-grounded audits, strategy, budget and measurement planning, creative production, experiments, reporting, monitoring, and explicitly approved campaign changes. Also trigger on PPC, paid social, retail media, attribution, tracking, landing pages, cross-platform conversion totals, negative keywords or search terms, beta-feature scoring, stale platform claims, API-token or credential setup, campaign deletion, and safe Claude Ads installation or uninstall.
references/platform-specs.md
View on GitHub# Creative Specification Resolution
**Verified:** 2026-10-07 for the retained RSA facts (`CLM-0100`, `CLM-0101`); the Meta Reels entry point was rechecked 2026-10-12; the Amazon and Reddit entries could not be rechecked 2026-10-12 and stay unverified
**Refresh due:** 2026-11-06
**Evidence status:** source index and validation workflow, not a universal spec sheet
Creative requirements vary by format, placement, objective, geography, account
eligibility, and product release. Resolve the exact format before validating an
asset. A single “platform spec” table is unsafe because it silently merges
requirements that do not apply to the same placement.
## Resolution order
1. Capture platform, objective, format, placement, destination, geography, and
the current account UI selection.
2. Open the matching platform-specific creative reference.
3. Verify volatile limits against the current official help page or API schema.
4. Prefer the stricter requirement when an asset must serve across placements.
5. Preview in the account UI and validate the rendered crop, overlays, text,
captions, audio, CTA, disclosure, and destination.
6. Record source ID, retrieval date, observed UI/API version, and exceptions.
If sources disagree, do not guess. Label the check `unknown`, preserve both
values, and request a current preview or API validation.
## Current source entry points
| Platform | First-party source | Scope |
| --- | --- | --- |
| Google / YouTube | `google-rsa-official`: [Responsive search ads](https://support.google.com/google-ads/answer/7684791) and [Google Ads asset requirements](https://support.google.com/adspolicy/answer/6368661) | Search text and general asset policy |
| Meta | `meta-video-ads-official`: [Meta Reels ads](https://www.facebook.com/business/ads/facebook-instagram-reels-ads) | Reels creative guidance and format discovery (page loaded 2026-10-12; it carries vendor performance claims that are not used here) |
| LinkedIn | `linkedin-ads-guide-official`: [LinkedIn Ads Guide](https://business.linkedin.com/advertise/ads/ads-guide) | Current format entry points |
| TikTok | `tiktok-ad-format-policy-official`: [Ad format and functionality](https://ads.tiktok.com/resources/help/article/tiktok-ads-policy-ad-format-and-functionality) | Creative and editorial requirements |
| Microsoft | `microsoft-ad-types-official`: [ResponsiveSearchAd schema](https://learn.microsoft.com/en-us/advertising/campaign-management-service/responsivesearchad?view=bingads-13) | Current v13 responsive-search-ad behavior |
| Apple | `apple-ads-creative-official`: [Apple Ads resources](https://ads.apple.com/app-store/resources) | Apple Ads resources and creative entry points |
| Amazon | `amazon-creative-acceptance-official`: [General requirements](https://advertising.amazon.com/help/GDG2CCTRU55BYY2Y) | Amazon Ads general creative requirements (page rendered only a site shell on 2026-10-12, so bind each rule to a directly readable Amazon page) |
| Reddit | `reddit-ads-help-official`: [Reddit Ads Help](https://business.reddithelp.com/s/) | Current Reddit help and policy discovery (the help root rendered only a loading shell on 2026-10-12, so use topic-specific pages) |
| Pinterest | `pinterest-ad-specs-official`: [Pinterest ad specs](https://help.pinterest.com/en/business/article/pinterest-product-specs) | Pinterest formats and assets |
| Snapchat | `snap-creative-specs-official`: [Snap creative specifications](https://forbusiness.snapchat.com/advertising/ad-formats) | Snap ad-format entry point |
| X | `x-creative-specs-official`: [X Ads creative specs](https://help.x.com/en/business-and-advertising/creative-ad-specifications) | X formats and assets |
These pages are discovery points, not proof that every format is available in a
given account. Re-check the active UI/API before emitting a pass or a mutation.
## Precisely retained facts
Google's current responsive-search-ad documentation says an RSA can accept up to
15 headlines and four descriptions, and headline fields support up to 30
characters. Microsoft's current v13 schema says its RSA accepts three to 15
headlines and two to four descriptions. These facts apply only to those named formats;
they do not establish a cross-platform text standard.
## Validation output
For each asset return:
- `platform`, `format`, `placement`, `objective`, and `geography`.
- Observed dimensions, duration, file type, file size, text fields, audio,
captions, destination, CTA, and disclosure.
- `pass`, `fail`, `unknown`, or `not_applicable` for each applicable requirement.
- Official source ID and retrieval date for every precise limit.
- Preview evidence and any crop or overlay risk.
- Remediation that preserves the creative concept.
## Non-universal rules
- There is no universal vertical-video safe zone. Validate against the current
placement preview and platform overlay guidance.
- Recommended sizes are not always minimum acceptance requirements; label them.
- A platform upload success is not proof of policy approval or good rendering.
- Character counts may use platform-specific normalization; validate through the
platform API/UI when exact acceptance matters.
- Do not turn “best practice” asset counts or durations into compliance failures.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |