Execute GWI MCP v2beta tool calls
JSON-RPC endpoint for the v2beta MCP profile. Supported tools:
- global_filters
- audience_generation
- generate_insights
- explore_insight
- list_datasets
- search_audiences
Authorizations
Format: Bearer YOUR_TOKEN
Body
JSON-RPC request for any supported v2beta MCP tool
- global_filters
- audience_generation
- generate_insights
- explore_insight
- list_datasets
- search_audiences
Resolve location and wave filters. Required before audience_generation, search_audiences (when used in the same workflow), and generate_insights.
Response
JSON-RPC response. HTTP 200 means the JSON-RPC call was processed, not that the tool succeeded.
Inspect result.isError if present:
true— tool failed; the message is inresult.content[0].text, andresult._meta.isInternalErrormay betruefor internal or timeout-style failures.
See Tool errors (result.isError) in the overview above for full behavior.
JSON-RPC 2.0 success envelope for MCP tools/call (no top-level error field).
When the tool fails, HTTP status is still typically 200 and this object is returned with result.isError: true. Use that flag rather than HTTP status alone.
2.0 Request identifier echoed back
MCP tool result. Inspect isError for tool-level success or failure.
isError: true — the tool failed; content usually has one text item with a human-readable explanation. Typical causes:
- Invalid arguments (e.g. empty
prompt, invalid UUID forinsight_idwhere required). - Downstream errors (e.g. resource not found, timeout, cancelled request, or generic internal failure).
_meta.isInternalError — when present and true, the server classified the failure as internal or timeout-style. Omitted or false for most validation and not-found style errors.
This is not the same as a JSON-RPC protocol error: invalid method or malformed requests use the standard JSON-RPC error field instead of a tool result.

