docs(creative): clarify creative-agent role in the sync_creatives flow#5821
Conversation
sync_creatives appears in both the Creative Protocol and the Media Buy Protocol and users conflate the two receiving roles. Add an Integration with the Media Buy Protocol section to the creative-agent implementation guide: sales agents accept sync_creatives to traffic creatives into media buys; creative agents optionally accept it as a library on-ramp; the build, traffic, deliver flow shows where each endpoint sits. Closes adcontextprotocol#5806.
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
There was a problem hiding this comment.
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final gh pr review). A human reviewer should take this PR.
This is an automated message from the Argus AI review workflow.
bokelley
left a comment
There was a problem hiding this comment.
Cross-checked against the Creative Protocol roles and sync_creatives task reference. The section correctly distinguishes optional creative-agent library intake from sales-agent trafficking and describes the buyer flow without changing wire behavior. Ready to merge.
Summary
Closes #5806 (critical knowledge gap: Integration with Media Buy Protocol).
Users conflate the two receiving roles of
sync_creativesbecause the task appears in both the Creative Protocol and the Media Buy Protocol. The issue's auto-proposed text says a buyer'ssync_creativescall "triggers your Creative Agent to receive creative synchronization requests", which is not how the protocols compose: trafficking calls go to the sales agent, and a creative agent only seessync_creativesif it opted into the library on-ramp. This PR adds the correct clarification instead.Change
New "Integration with the Media Buy Protocol" section in
docs/creative/implementing-creative-agents.mdx, placed after the optionalsync_creativestask:build_creative/list_creatives.Docs only, outside
docs/reference/; no changeset per the protocol-scope policy.Verification
docs/creative/specification.mdx(task list and sync_creatives requirements),docs/creative/task-reference/sync_creatives.mdx, anddocs/creative/sales-agent-creative-capabilities.mdx