Docs/MCP reference

players_list

Read only

Players the project has seen, as pseudonymous per-game ids (never an account, email or wallet): player, kind (account for a player signed in to Looping, or guest), name, last_seen, and banned_until with ban_reason while a ban is in force.

GET/api/agent/players

Behavior

Players the project has seen, as pseudonymous per-game ids (never an account, email or wallet): player, kind (account for a player signed in to Looping, or guest), name, last_seen, and banned_until with ban_reason while a ban is in force. banned true lists current bans only; limit is 1-200. Use it to find the id a report names before player_ban, and to check that a ban or a lift landed.

Input parameters

limitOptional
integer
  • Minimum: 1
  • Maximum: 200
bannedOptional
boolean

The descriptions above include conditional requirements. The full schema below shows structural validation; runtime checks also apply.

JSON Schema

Input schema · draft-7
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    },
    "banned": {
      "type": "boolean"
    }
  },
  "additionalProperties": false
}
Calling this tool

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.