world_revert
DestructiveUndo one player's changes to a world since a time in the last 30 days (since: an ISO time or milliseconds), chunk by chunk: every chunk the player changed goes back to how it was before their first change.
/api/agent/worlds/revertBehavior
Undo one player's changes to a world since a time in the last 30 days (since: an ISO time or milliseconds), chunk by chunk: every chunk the player changed goes back to how it was before their first change. Without apply it changes nothing and lists the chunks with any later changes other players made in them, which a revert loses too; tell the creator, then call again with apply: true. Chunks whose earlier value is no longer kept are listed as unrecoverable (world_restore reaches further).
player is a w… or g… id from players_list, a report or worlds_status' changes.
Input parameters
worldRequiredstring- Pattern: ^[a-z0-9][a-z0-9-]{0,62}$
playerRequiredstring- Pattern: ^[gw][a-f0-9]{16}$
sinceRequiredstring | integerNested schema
{
"anyOf": [
{
"type": "string",
"minLength": 10,
"maxLength": 40
},
{
"type": "integer",
"exclusiveMinimum": 0,
"maximum": 9007199254740991
}
]
}applyOptionalbooleanreasonRequiredstring- Min. length: 3
- Max. length: 300
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": {
"world": {
"type": "string",
"pattern": "^[a-z0-9][a-z0-9-]{0,62}$"
},
"player": {
"type": "string",
"pattern": "^[gw][a-f0-9]{16}$"
},
"since": {
"anyOf": [
{
"type": "string",
"minLength": 10,
"maxLength": 40
},
{
"type": "integer",
"exclusiveMinimum": 0,
"maximum": 9007199254740991
}
]
},
"apply": {
"type": "boolean"
},
"reason": {
"type": "string",
"minLength": 3,
"maxLength": 300
},
"env": {
"type": "string",
"enum": [
"public",
"preview"
]
}
},
"required": [
"world",
"player",
"since",
"reason"
],
"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.