Skip to content

Conversation

@bokelley
Copy link
Contributor

@bokelley bokelley commented Aug 5, 2025

Summary

This PR introduces the Creative Agent Protocol to AdCP, providing a comprehensive framework for AI-powered creative generation and management. The protocol supports two primary use cases:

  1. Static Asset Generation (Manifest Mode): Generates structured creative manifests for traditional ad servers
  2. Live Creative Agent Deployment (Code Mode): Produces executable code for real-time, dynamic creative generation

Key Changes

New Tools

  • build_creative: A conversational tool for creative generation with iterative refinement capabilities
  • manage_creative_library: Comprehensive asset management with tagging, search, and organization features

Documentation

  • Added Creative Agent Protocol specification explaining the two output modes
  • Created "Why Creative Agents" document explaining the brand benefits
  • Integrated AdCP flow diagram showing how creative agents fit into the ecosystem
  • Updated API reference with new tools and their complete specifications

Key Features

  • Conversational workflow: Natural message-based interaction for creative refinement
  • Real-time inference: Support for dynamic creative optimization at ad request time
  • Asset tagging: Organized asset management with flexible tagging system
  • Format flexibility: Support for both standard format IDs and custom format definitions
  • Preview generation: Rendered preview examples for both manifest and code outputs

Technical Details

The protocol maintains clear separation between:

  • Protocol specification (abstract interfaces and workflows)
  • Implementation details (left to individual implementers)

Both tools integrate seamlessly with existing AdCP workflows:

  • Creative manifests feed into add_creative_assets
  • Creative agents participate in the media buy flow
  • Asset libraries provide reusable components across campaigns

Testing

All changes have been validated:

  • Documentation builds successfully
  • Examples demonstrate both static and dynamic workflows
  • API specifications are complete and consistent

🤖 Generated with Claude Code

@bokelley bokelley force-pushed the creative-build-single-tool branch from 997931f to 35fe439 Compare September 16, 2025 00:40
bokelley and others added 3 commits September 27, 2025 10:05
…tive_library tools

- Add build_creative tool for conversational creative generation
- Support two output modes: manifest (static) and code (dynamic)
- Add manage_creative_library tool for asset management with tagging
- Include real-time inference capabilities for dynamic creative optimization
- Add documentation explaining why creative agents matter for brands
- Update API reference and navigation structure
- Add AdCP flow diagram to intro page

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
…emas

- Address user review comments:
  * Fix "publishers" to "advertisers" for asset library ownership
  * Restructure format parameter to format_source + format_id for clear discovery
  * Use generic "asset providers" language for broader applicability

- Create missing JSON schemas:
  * build-creative-request.json and build-creative-response.json
  * manage-creative-library-request.json and manage-creative-library-response.json
  * asset-type.json core schema for format requirements

- Improve format discovery architecture:
  * Add format lookup documentation explaining discovery process
  * Support both standard AdCP formats and publisher-specific formats
  * Leverage existing list_creative_formats tool for format resolution

- Remove platform-specific references:
  * Replace TikTok example with generic short-form video format
  * Maintain platform-agnostic approach aligned with format standardization

- Update schema registry with new Creative Agent Protocol schemas

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
The creative-agent-protocol.md file was linking to the old tasks/ directory.
Updated to use the new task-reference/ directory structure.

Fixes CI build failure due to broken links check.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@bokelley bokelley force-pushed the creative-build-single-tool branch from c4b2042 to a0f1c4a Compare September 27, 2025 14:07
bokelley and others added 2 commits September 27, 2025 11:24
…a inconsistencies

- Promote Creative Protocol to top-level navigation alongside Signals and Media Buy protocols
- Create comprehensive getting-started guide for Creative Protocol
- Move all creative documentation from media-buy/ to creative-protocol/ directory
- Simplify build-creative-response security requirements from complex conditional to optional field
- Fix schema version inconsistencies: update all media-buy request schemas from 1.5.0 to 1.6.0
- Update intro.md and sidebars.ts to reflect new Creative Protocol structure
- Remove outdated creative-agent-protocol.md in favor of simplified index.md

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
GitHub Actions was failing because the fly-deploy workflow was using
Node.js v18.20.8 while the project requires Node.js >=20.0. Updated
to match the schema-validation workflow which already uses Node.js 20.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@bokelley bokelley merged commit becaf42 into main Sep 27, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants