Rankings listing
get_rankingsThe FULL published ranking table in rank order for one system, from the newest week at or before as_of. Rows carry player_name as published and a null player_id for players outside our roster, so the table has no silent holes. ATP/WTA history runs deep. The ITF circuits begin 2026-07-29. For point-in-time records of SPECIFIC players use get_player_rankings. Requires the PRO plan.
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": {
"system": "<system>"
},
"name": "get_rankings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| as_of | No | YYYY-MM-DD. Serves the newest published week at or before this date. Omit for latest. | |
| limit | No | Maximum ranking rows to return (1-200). | |
| system | Yes | Ranking system to list. utr has no listing, because it is a rating, not a ranking. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | True when the request succeeded, including when the answer is an empty list. False for a missing or rejected key, a plan that does not include this data, an unknown id, a rate limit or a network error. The message then says what to do. check_api_status is the exception: it is true whenever the API answered, and reports API key problems in the message. | |
| message | Yes | Human-readable summary of the result, safe to relay to the user verbatim. | |
| rankings | No | The table in rank order. |