Overview
Key features:- Filter by format, status, tags, dates, assignments, concepts, and variables
- Sort by creation date, update date, name, status, or assignment count
- Cursor-based pagination for large libraries
- Optionally include assignments, delivery snapshots, items, and dynamic creative optimization (DCO) variables
- Return only specific fields to reduce response size
- Filter by creative concept (groups of related creatives across sizes/formats)
- Find DCO creatives and inspect their dynamic content slots
Request parameters
Schema:creative/list-creatives-request.json
Core parameters
Data inclusion options
Filtering options
Thefilters object supports these optional, composable filters:
* Assignment-related filters are specific to sales agents. Standalone creative agents ignore these.
Archived creatives are excluded by default. To include archived creatives in results, explicitly include
"archived" in the statuses array. Suspended creatives are not archived; include "suspended" when you specifically want recoverably offline creatives such as published-post references with expired authorization.For published-post reference products,
list_creatives is limited to the downstream publisher identities the seller is authorized to inspect. If a product requires a second platform connection such as publisher_identity and it is missing, the seller should return AUTHORIZATION_REQUIRED with error.details.missing_connections[]. It should not present list_creatives as global platform post search.Sorting options
Sort results by various fields with ascending or descending order:created_date- When the creative was created (default)updated_date- When creative was last modifiedname- Creative name (alphabetical)status- Approval statusassignment_count- Number of package assignments
Pagination
Control result set size with cursor-based pagination:Response format
Schema:creative/list-creatives-response.json
The response provides creative data with optional enrichment:
Per-creative fields
Pricing
Wheninclude_pricing=true and account is provided, each creative includes pricing_options from the account’s rate card:
pricing_option_id (from the build_creative response) in report_usage for billing verification. Vendors may offer multiple options — volume/commitment tiers, context-specific rates (premium vs. standard placements), or entirely different pricing models for different product lines. This is the same pattern used by signals and content standards.
Delivery snapshot
Wheninclude_snapshot=true, each creative includes a lightweight delivery snapshot for operational questions like “is this creative active?” or “when did it last serve?” This is not analytics — for detailed performance data, use get_creative_delivery.
Purged tombstones
When a creative is destroyed viacreative.purged with purge_kind: soft, the seller retains a tombstone for 30 days from the purge timestamp. The tombstone surfaces on list_creatives only when the request sets include_purged: true:
status field on a tombstone is frozen at its pre-purge value (in the example above, "approved" is what the creative was right before purge — not a current claim). Buyers MUST treat the creative as gone: assignments, serving operations, and delivery reads no longer apply. The presence of the purge block is the unambiguous signal.
Hard-purged creatives (purge_kind: hard, used for legal erasure under GDPR Article 17 / CCPA / equivalent) retain no tombstone; the creative.purged webhook is the only signal. See snapshot-and-log § Rule 4 carve-out for the rationale.
Webhook activity
Wheninclude_webhook_activity: true, each returned creative carries a webhook_activity[] array of the most recent fires scoped to that creative — creative.status_changed and creative.purged deliveries. This is the buyer’s debug surface for “did the publisher fire? did my endpoint receive it? was the retry trail clean?” — the same shape and contract as webhook_activity[] on get_media_buys. See Webhook activity log pattern for the full normative contract (retention, three-state presence, request-field conventions).
To subscribe to these fires, register a notification_configs[] entry on the account via sync_accounts. The seller fires per-subscriber against each entry whose event_types[] includes the type. webhook_activity[] on this read is the buyer-side debug log of what actually fired.
Three-state presence applies:
- Field omitted — seller does not surface webhook activity on this read.
[]— seller surfaces the field but no fires fall in the retention window for this creative.- Non-empty — actual records, most recent first, capped at
webhook_activity_limit(max 200).
idempotency_key. Each record’s notification_type discriminates the fire kind:
list_accounts.accounts[].notification_configs[] — is the right URL active with the right event_types[]? — and (b) seller capability declaration via get_adcp_capabilities — does the seller support the event types I subscribed to? Field omission on webhook_activity alone does not distinguish “seller doesn’t surface the log” from “no fires occurred.”
Buyer handler (end-to-end)
A buyer’s webhook handler forcreative.status_changed correlates each fire with library state via creative_id, dedupes on idempotency_key, and re-reads list_creatives for the authoritative snapshot (per snapshot-and-log Rule 3):
Account requirements
Creative agents that host a library should implement the accounts protocol (
sync_accounts / list_accounts) so buyers can establish access before querying creatives. This is the same accounts protocol used by sales agents for media buys — there is no separate version. Sales agents that already implement the accounts protocol for media buys do not need to do anything additional.Examples
Concept-scoped query with variables
List all approved creatives in a specific concept, including DCO variable definitions:Format-specific query
Find creatives matching specific format IDs across concepts:Find DCO creatives
Find creatives with dynamic content variables for personalized campaigns:Field-limited query
Get minimal creative data for a selection dropdown:Library health check
Find active creatives with delivery snapshots to identify stale or dormant assets:Related tasks
get_creative_delivery- Detailed performance analytics with date ranges, variant breakdowns, and full delivery metricsbuild_creative- Build manifests from library creatives or generate from scratchsync_creatives- Upload and manage creative assets on any agent hosting a creative librarylist_creative_formats- Discover supported creative formatspreview_creative- Generate previews of creative manifests