player_records
Read onlyOne signed-in player's verified records in this game, for support: their documents of each kind (up to 200 per kind), their counters, and the newest 50 changes, each with an entry id, what it was before and after, and the round or room result that made it.
/api/agent/records/playerBehavior
One signed-in player's verified records in this game, for support: their documents of each kind (up to 200 per kind), their counters, and the newest 50 changes, each with an entry id, what it was before and after, and the round or room result that made it. player is the w… id from players_list; env preview for the records behind the preview host. Read it when a player reports a lost or wrong record, then record_restore the entry that changed it.
Input parameters
playerRequiredstring- Pattern: ^w[a-f0-9]{16}$
envOptional"public" | "preview"The descriptions above include conditional requirements. The full schema below shows structural validation; runtime checks also apply.
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"properties": {
"player": {
"type": "string",
"pattern": "^w[a-f0-9]{16}$"
},
"env": {
"type": "string",
"enum": [
"public",
"preview"
]
}
},
"required": [
"player"
],
"additionalProperties": false
}Use its name in your connected MCP client. For the HTTP API, the route is relative to your Convex site URL and requires your agent key as a bearer token. Keep the key on the agent side, outside a game build.