Get metric timeseries

MCPget_metric_timeseriesREAD$0.04 / call

One headline metric BY DAY (PRO) — the trend, not the snapshot every other analytics tool returns. Use it to answer 'is this getting worse' and to line a turn up against a release date. Days built on very few visits are flagged thin: read the shape, never a single point.

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)

metricstringoptional

Which metric to plot (default: dead_end_rate) One of: dead_end_rate, self_serve_resolution_rate, visits, success, dead_ends, median_time_to_first_value.

Call it#

MCPcurl

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

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_metric_timeseries","arguments":{"metric":"dead_end_rate"}}}'

Updated Sep 19, 2026