Recorded ADP player history
get_adp_historyOne player in one required slate. Free: seven days of daily history; Developer: recorded daily history; Production/Scale: hourly. No interpolated dates or implied pre-collection history.
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_id": "<player_id>",
"slate": "<slate>"
},
"name": "get_adp_history"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Inclusive New York date. | |
| from | No | Inclusive New York date. | |
| limit | No | Requested rows, default 50, maximum 500; oversized values are rejected. | |
| slate | Yes | Tracked public slate ID. ADP is specific to this slate. | |
| cursor | No | Opaque cursor bound to filters and snapshot. Hourly current boards cannot be paged. | |
| interval | No | Free: daily seven-day window. Developer: all recorded daily history. Production/Scale: hourly. | day |
| player_id | Yes | Stable public player ID from an ADP board. | |
| user_request | No | Optional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private. |