Get goal journeys

MCPget_goal_journeysREAD$0.04 / call

Everyone who completed one goal, with how long they took from first seen to converting (PRO). Quotes MEDIAN and p90, never a mean: time-to-convert on a docs site is bimodal — readers who arrive ready and readers who evaluate for weeks — and the mean lands in the empty valley between the two modes, describing a visitor who does not exist. Both are withheld under 5 conversions, where the list itself is the answer. The source shown is LAST TOUCH and over-credits Direct; treat it as a hint, not attribution.

Arguments

workspace_idstringoptional

Workspace ID (optional when MCP endpoint is auto-scoped). Numeric workspace id — OR the project as the user names it: 'owner/repo', the repo name alone, the site's display name, its docs URL or custom domain. Text is resolved server-side; an ambiguous name returns the candidates instead of guessing, so pass what the user said rather than calling list_workspaces first.

goalstringoptional

Goal name. Defaults to the most-completed goal.

periodstringoptional

Time range (default: 7d)

limitintegeroptional

Max rows (default 100-200)

Call it#

MCPcurl

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_goal_journeys",
    "arguments": {}
  }
}

curl -X POST 'https://docsbook.io/api/mcp/server' \
  -H 'Authorization: Bearer dbk_YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_goal_journeys","arguments":{}}}'

Updated Sep 19, 2026