Playbook & Feedback
Read and regenerate the workspace’s campaign playbook, and submit product feedback.
Tools (3)
Section titled “Tools (3)”get_playbook
Section titled “get_playbook”Full name: campaignstack_get_playbook
Get the workspace’s playbook as playbookSections, one field per section: identity (sent on every message), voice (sent on every message), boundaries (sent on every message), angles (sent on messages we send first), objections (sent on replies, after they have written back). Also returns offerContext, the factual company/offer grounding injected into every AI craft regardless of playbook resolution, and capabilities, the description of what the system behind the workspace can detect and do that is injected into reply crafts only. All three are editable via campaignstack_update_workspace. Returns null if the workspace does not exist; an unwritten playbook comes back as an empty object. Use campaignstack_regenerate_playbook to create or refresh it.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
workspaceId | string | No | — | Defaults to the API key’s workspace |
regenerate_playbook
Section titled “regenerate_playbook”Full name: campaignstack_regenerate_playbook
Trigger AI regeneration of the workspace playbook based on current campaigns, ICPs, personas, and company context. An existing playbook is UPDATED, not discarded: user-authored passages are preserved verbatim and the previous version is snapshotted to history (see campaignstack_list_playbook_versions / campaignstack_revert_playbook). An existing hand-edited offerContext is never overwritten. The operation is NOT idempotent and may take several seconds. Fetch the updated playbook afterwards with campaignstack_get_playbook.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
workspaceId | string | No | — | Defaults to the API key’s workspace |
submit_feedback
Section titled “submit_feedback”Full name: campaignstack_submit_feedback
Submit a feedback report or bug report to the CampaignStack team. Mirrors the in-app feedback widget (feedback-widget.tsx) and writes to the same feedbackReports table and triggers the same email notification. Use category ‘bug’ for broken functionality, ‘feature’ for capability requests, ‘question’ for how-to questions, and ‘other’ for anything else. Returns the new feedback report ID.
Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
workspaceId | string | No | — | Defaults to the API key’s workspace |
category | bug | feature | question | other | Yes | — | Feedback category: bug (something broken), feature (new capability request), question (how-to), other |
message | string | Yes | — | The feedback body text (min length: 1) |
route | string | Yes | — | The app route or context where the feedback originates (e.g. ‘/dashboard/campaigns’ or ‘mcp-agent’) (min length: 1) |