world_reset
DestructiveWipe one world now, as its scheduled wipe would: every chunk cleared, a new seed, the epoch raised; players in it are told and their game regenerates.
/api/agent/worlds/resetBehavior
Wipe one world now, as its scheduled wipe would: every chunk cleared, a new seed, the epoch raised; players in it are told and their game regenerates. It is recoverable with world_restore for 30 days. reason is kept in the project's log. Wiping a world players built in is the creator's decision: confirm it with them first.
Input parameters
worldRequiredstring- Pattern: ^[a-z0-9][a-z0-9-]{0,62}$
reasonRequiredstring- 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}$"
},
"reason": {
"type": "string",
"minLength": 3,
"maxLength": 300
},
"env": {
"type": "string",
"enum": [
"public",
"preview"
]
}
},
"required": [
"world",
"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.