Skip to content

docs(creative): clarify creative-agent role in the sync_creatives flow#5821

Open
aleksUIX wants to merge 2 commits into
adcontextprotocol:mainfrom
aleksUIX:docs/creative-agent-sync-creatives-relationship
Open

docs(creative): clarify creative-agent role in the sync_creatives flow#5821
aleksUIX wants to merge 2 commits into
adcontextprotocol:mainfrom
aleksUIX:docs/creative-agent-sync-creatives-relationship

Conversation

@aleksUIX

@aleksUIX aleksUIX commented Jul 6, 2026

Copy link
Copy Markdown

Summary

Closes #5806 (critical knowledge gap: Integration with Media Buy Protocol).

Users conflate the two receiving roles of sync_creatives because the task appears in both the Creative Protocol and the Media Buy Protocol. The issue's auto-proposed text says a buyer's sync_creatives call "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 sees sync_creatives if 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 optional sync_creatives task:

  • One task, one schema, two receiving roles: sales agents accept it to traffic creatives (library upload, package assignment, review pipeline); creative agents MAY accept it as an optional library on-ramp feeding build_creative / list_creatives.
  • A build, traffic, deliver walkthrough showing that the creative agent is not in the path of the trafficking call, while its published format definitions are what the sales agent validates against.
  • Pointer to the existing dual-role page for sales agents that implement both protocols on one endpoint.

Docs only, outside docs/reference/; no changeset per the protocol-scope policy.

Verification

  • Content checked against docs/creative/specification.mdx (task list and sync_creatives requirements), docs/creative/task-reference/sync_creatives.mdx, and docs/creative/sales-agent-creative-capabilities.mdx
  • Internal links resolve to existing pages

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.

@aao-release-bot aao-release-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Argus review could not complete

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.

View workflow run

This is an automated message from the Argus AI review workflow.

@aao-release-bot aao-release-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Argus review could not complete

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.

View workflow run

This is an automated message from the Argus AI review workflow.

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.

docs: knowledge gap (critical) — Integration with Media Buy Protocol

1 participant