campaign-from-brief

Campaign from a brief (server-side)

Runtime contract

• Delivery: composite
• Minimum Agent Connect key scope: send
• Minimum subscription tier: business
• Authentication: send the tenant-bound Agent Connect key as a Bearer token.
• Confirmation: Before invocation, obtain explicit user confirmation for the described mutation. A key scope grants technical permission; it is not user consent.
• Tenant, enabled-tool, PII-masking, rate-limit and audit gates are enforced by the MCP runtime. Never bypass or reproduce them client-side.
• Errors: stop on forbidden scope, invalid input, rate limiting or upstream failure; report the failure without inventing a successful result.
• Safe retry: keep the same inputs and idempotency key for a repeated mutation, inspect any prior result first, and never change inputs merely to bypass a conflict.

Workflow

Campaign from a brief (server-side composite)

This is a composite playbook: its steps run SERVER-SIDE and ENCAPSULATED by the MCP gateway (issue #5197). The calling agent only triggers playbook_campaign-from-brief with inputs -- the orchestration below is executed by the server, not the customer LLM, and is never exposed as raw prompt.

What it does

Turns a one-line campaign brief into two linked artifacts the user can review before anything goes out:

1. Segment -- calls create_segmentation to create a named audience segmentation from the brief. The brief text is stored as the segment description so the intended audience and goal are captured alongside the campaign.
2. Draft -- calls create_broadcast to create a broadcast (draft, sendStatus defaults to draft) on the target channelId carrying the campaign copy.

The broadcast is created as a DRAFT: this playbook prepares the campaign, it does not dispatch it. The user (or a separate, explicitly-confirmed send step) reviews audience + copy before any message reaches recipients.

Inputs

• channelId (number, required) -- channel the campaign broadcast is drafted on.
• segmentName (string, required) -- name of the audience segment.
• brief (string, required) -- audience + goal, stored as the segment description.
• message (string, required) -- campaign copy (max 4096 characters).