Player rankings as of a date
get_player_rankingsPoint-in-time ranking records for SPECIFIC players. Per system, the newest record in force ON OR BEFORE as_of, never one dated after it. Every other ranking field in this API is the CURRENT value joined at read time. This one is the historical answer. Systems are never collapsed: ATP/WTA and the ITF circuits carry rank+points, UTR a rating. ITF and UTR history begins 2026-07-29. Requires the ULTRA 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": {
"player_ids": "<player_ids>"
},
"name": "get_player_rankings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| as_of | No | YYYY-MM-DD. The record in force on this date. Omit for the latest known. | |
| system | No | Restrict to one system. Omit for every system held for the player. | |
| player_ids | Yes | Roster player ids, as returned by search_players. Max 50. |
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. | |
| coverage | No | What resolved against what was asked (players_resolved, systems_resolved, oldest_available per system). Read before trusting an empty result. | |
| rankings | No | One record per player × system held. |