Create campaign
create_campaignCreate a campaign: a named, dated content schedule in the workspace. Inputs: name, start_date (ISO 8601 date), length_weeks; optional brief, topics, call_to_action, target_link.
Without topics, Blaze generates the campaign's theme, audience, call to action, and topics from the brief in the background; the tool returns the campaign id right away, and list_campaigns shows the topic count once generation finishes. With topics, those are used as given and nothing is generated. After that, Blaze generates content for the campaign's posting schedule, as it does for campaigns created in the Blaze app.
Pass the returned id to generate_post as brand_plan_schedule_id to add a post to this campaign. Requires the workspace to have an active brand plan and an admin member.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"workspace_key": "<workspace_key>",
"name": "<name>",
"start_date": "<start_date>",
"length_weeks": "<length_weeks>"
},
"name": "create_campaign"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Display name for the campaign. | |
| brief | No | What the campaign is about. Seeds theme/topic generation. Omit to generate from the brand context. | |
| topics | No | Optional explicit topics. If given, these are used and topic generation is skipped; otherwise topics are generated for you. | |
| start_date | Yes | ISO 8601 date the campaign starts. | |
| target_link | No | Optional URL the campaign drives to. | |
| length_weeks | Yes | Number of weeks the campaign spans. | |
| workspace_key | Yes | Key of the workspace to act in. Call list_workspaces to see the workspaces you have access to and their keys. | |
| call_to_action | No | Optional call to action text. |