Create a Storyworld

storyworld_create: permissions and generated input/output contracts.

storyworld_create · Gateway release 0.8.3

Create a new Storyworld owned by the connected account. Search first. Retry the identical operationId after a lost response; this does not generate media or spend credits.

Required scopes: account:read, studio:write. Changes saved state or requests work; review the operation’s effects.

Availability depends on runtime configuration and the permissions granted to this connection. Use live MCP discovery as the authority.

​

Input

{
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "title": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200
    },
    "description": {
      "type": "string",
      "minLength": 1,
      "maxLength": 2000
    },
    "operationId": {
      "type": "string",
      "pattern": "^[a-zA-Z0-9-]{16,64}$",
      "description": "Persist a client-generated UUID before this mutation. Repeat identical inputs and this same ID after interruption; a new ID is a new request."
    }
  },
  "required": [
    "title",
    "operationId"
  ]
}

​

Declared output

This is the declared success schema. Error results and binary media blocks are separate MCP protocol results.

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "schemaVersion": {
      "type": "string",
      "const": "1"
    },
    "storyworldId": {
      "type": "string",
      "pattern": "^[a-f0-9]{24}$"
    },
    "created": {
      "type": "boolean"
    }
  },
  "required": [
    "schemaVersion",
    "storyworldId",
    "created"
  ],
  "additionalProperties": {}
}

All tools · Permissions · Media and recovery