Create funnel
MCP
create_funnelWRITE$0.00001 / call
Features
Define an ORDERED route through the docs, as a list of goal names. Order is the whole point: a visit counts as reaching step N only if it hit steps 1..N in sequence, so a reader who lands on step 3 first is not counted. Two rules the validator enforces and you should follow when proposing one: start BROAD (most docs readers arrive deep from search or an AI answer, and a narrow step 1 excludes the majority of traffic before measuring anything), and end on a REAL OUTCOME (a funnel ending on a scroll measures attention, not results). window_hours bounds how long after step 1 a later step still counts; omit it to use the visit itself, which is the honest default for docs.
Input5
Your API key, for the REST call. Sent from your browser straight to the API — never to Docsbook, never stored.
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.
Machine name, e.g. 'evaluation'.
Goal names, in order. Between 2 and 8. Create the goals first with create_goal.
Human label. Defaults to the key.
Conversion window in hours. Clamped to what the plan retains — a window longer than your history can never complete.
Output3
Example input
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "create_funnel",
"arguments": {
"key": "<key>",
"steps": []
}
}
}Example output
{
"workspace_id": 0,
"funnel": {},
"issues": []
}