looping.gg

Docs/MCP reference

score_remove

Write

Take one score off the game's leaderboard (score_id from leaderboard_read), for example a cheated or test score.

POST/api/agent/scores/remove

Behavior

Take one score off the game's leaderboard (score_id from leaderboard_read), for example a cheated or test score. reason is for the creator and operators, never shown to players. The score stays recorded, so its round cannot be posted again; restore true puts back a score removed this way (one rejected by replay verification stays off). To stop a player posting at all, use player_ban. Removing someone's score is the creator's decision: confirm it with them first.

Input parameters

score_idRequired
string
  • Min. length: 10
  • Max. length: 64
reasonRequired
string
  • Max. length: 200
restoreOptional
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": {
    "score_id": {
      "type": "string",
      "minLength": 10,
      "maxLength": 64
    },
    "reason": {
      "type": "string",
      "maxLength": 200
    },
    "restore": {
      "type": "boolean"
    }
  },
  "required": [
    "score_id",
    "reason"
  ],
  "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.