AdCP: publisher-side brief execution
Receive a brief in the open AdCP standard and execute it on your GAM network through your MCP tools. No public endpoint, no buyer-agent authentication.
MCP tools
| Tool | Description | Credits |
|---|---|---|
| validate_adcp_request | Validate the advertising brief in AdCP format | 0 |
| preview_media_buy_from_adcp | Generate the media plan preview (no side effects) | 0 |
| create_media_buy_from_adcp | Deploy the Line Items and creatives matching the brief | 0 |
| get_products_adcp | Normalizes the product format to prepare the future exposure of a catalogue for AI agents | 0 |
Examples
AdCP brief validation
{
"tool": "validate_adcp_request",
"arguments": {
"brief": {
"advertiser": "BrandX",
"budget": 5000.0,
"format": "DISPLAY_MPU",
"targeting": {"countries": ["FR"]}
}
}
}Notes
- • AdCP (Ad Context Protocol) is an open standard from AgenticAdvertising.org; OrbiAds executes it on the publisher side, with no intermediation.
- • Validation and preview (adcp_validate & adcp_preview) have no advertising side effect.
- • Execution creates the entities in GAM atomically.
- • Budgets and permissions are isolated at the Firestore tenant level.
- • The product catalogue is not actively exposed; the AdCP tools normalize the flows in anticipation of future integrations.