mcpDeterministic

Validate campaign brief

tools/call

Run the deterministic brief quality gate (the parity enforcer): proof points must trace to real GTM case studies/offers, decision-tree conditions must reference declared signals, the value proposition must link to a distinct ICP pain, and audience size must be sane. Pass briefId (a stored brief) OR plan (a raw brief plan you authored locally) - exactly one. mode launch (default) demotes generation-quality findings to warnings; strict treats them as errors. Returns { valid, errors, warnings }. Always run this before activating a brief you reasoned yourself.

Parameters

workspaceId
string
Optional with an API key (inferred from the key).
briefId
string
Validate a stored brief by id. Mutually exclusive with plan.
plan
object
Validate a raw brief plan object (e.g. one a local agent just authored). Mutually exclusive with briefId.
mode
string
launch (default) or strict.
strict | launch

Example

MCP tools/calljson
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "validate-campaign-brief",
"arguments": {}
}
}

Response

The operation is available, but its typed response schema has not been published yet.

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.
Pipeline MCP documentation | Pipeline