mcpDeterministic

Launch prepared campaign

tools/call

Activate a campaign that was prepared by prepare-campaign-launch. Requires the exact expiring approvalId and confirm=true. Revalidates workspace ownership and campaign draft status, atomically consumes the approval, and starts delivery idempotently.

Parameters

workspaceId

string

Optional with API-key auth. Inferred from the key.

approvalIdrequired

string

Approval ID returned by prepare-campaign-launch.

confirmrequired

boolean

Must be true after the operator explicitly approves the preview.

Example

MCP tools/calljson

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "launch-prepared-campaign",
    "arguments": {
      "approvalId": "00000000-0000-4000-8000-000000000000",
      "confirm": true
    }
  }
}

Response

Success response schemajson schema

{
  "type": "object",
  "properties": {
    "launched": {
      "type": "boolean"
    },
    "reason": {
      "type": "string"
    },
    "campaignId": {
      "type": "string"
    },
    "prospectsUploaded": {
      "type": "number"
    },
    "sourceTableIds": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "channels": {
      "type": "object"
    }
  },
  "required": [
    "launched"
  ]
}

JSON-RPC errors

-32602: Invalid parameters. Field-level details are returned in the JSON-RPC error data.
-32001: Authentication or hosted AI consent is required.
-32003: Workspace access is denied.
-32029: The request was rate limited.