Get response times
get_response_timesRead a monitor's response-time series over 24h to 1y, optionally filtered by check location. Page through results with a cursor to analyze latency trends.
Instructions
Read response-time series for a monitor, optionally by city and country. Uses 5-minute windows for 24h, hourly up to 30d, daily beyond. Larger buckets report maxima of the recorded percentiles, not an exact percentile of raw requests. Follow next_cursor for all points.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"monitor": "<monitor>"
},
"name": "get_response_times"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum records in this page, from 1 to 100; defaults to 50. | |
| cursor | No | Call again with cursor set to the returned next_cursor until next_cursor is null. | |
| window | No | History window ending now, capped at 30 days without history_1y. The result reports the effective window. | 24h |
| monitor | Yes | Monitor id from list_monitors or create_monitor. | |
| location | No | Optional check location, using the city and country returned by get_incidents. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| series | Yes | ||
| window | Yes | ||
| monitor | Yes | ||
| resolution | Yes | ||
| aggregation | Yes | ||
| next_cursor | Yes |