Get route patterns

MCPget_route_patternsREAD$0.04 / call

The 2-4 page SEQUENCES readers actually walk (PRO), with how often each ends well. Top-pages reports cannot distinguish an intended journey from three unrelated landings — this can. A frequent route that keeps ending badly is a NAVIGATION defect (the next page readers need is not the one you link to), not a page-quality problem, so rewriting the pages will not fix it.

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.

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_route_patterns",
    "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_route_patterns","arguments":{}}}'

Updated Sep 19, 2026