RPG Maker MZ Authoring MCP

Overview Schema Source Related Servers Discussions Admin

update event page settings

update_event_page_settings

Patch RPG Maker MZ event page settings such as conditions, image, movement, flags, priority, and trigger; preview the validated change set first, then apply it when clean.

Instructions

Patch page settings. Fields: conditions {switch1|switch2: switchId|null, variable: {variableId, atLeast}|null, selfSwitch: "A".."D"|null, item: itemId|null, actor: actorId|null}; image {characterName, characterIndex 0-7, direction down|left|right|up, pattern 0-2, tileId}; movement {type fixed|random|approach|custom, speed 1-6, frequency 1-5, route {repeat, skippable, wait, commands}}; walkAnime, stepAnime, directionFix, through (booleans); priority below|same|above; trigger action_button|player_touch|event_touch|autorun|parallel. null disables a condition.

Preview-first: returns a change set (semantic + native diff, validation). Pass apply=true to commit immediately when the preview is clean.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mapId": "<mapId>",
      "eventId": "<eventId>",
      "pageIndex": "<pageIndex>",
      "settings": "<settings>"
    },
    "name": "update_event_page_settings"
  }
}

Input Schema

Name	Required	Description
`apply`	No	Commit right after a successful preview (non-destructive operations only; needs --allow-write; warnings also need acknowledgeWarnings). Default false = preview only.
`mapId`	Yes	Map ID (from list_maps)
`eventId`	Yes	Map event ID
`settings`	Yes	Settings patch
`pageIndex`	Yes	ZERO-based page index (Page 1 in the editor = pageIndex 0)
`allowScript`	No	true ONLY if the user explicitly asked to insert JavaScript (script commands, script conditions/operands, route scripts).
`description`	No	Optional description stored in the transaction log
`acknowledgeWarnings`	No	Accept validation warnings when apply=true. Review them with the user first.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, non-destructive, non-idempotent, and this description adds real behavior beyond them: the preview-first change-set return, the apply=true commit escape hatch, and the rule that null disables a condition. The significant remaining gap is patch semantics — it never says whether unspecified fields are preserved or reset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

There is no wasted prose, and the preview/commit note is a well-placed closer. However, the field enumeration is delivered as a dense pseudo-grammar with pipe and brace shorthand ("{switch1|switch2: switchId|null, ...}") that is slower to parse than a short bulleted list, and the two-word opening sentence is thinner front-loading than the tool deserves.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-object mutation tool with no output schema, the definition covers the settings vocabulary, the preview-first return contract, and the commit gate — enough to call it correctly. It is not fully complete: merge-vs-replace behavior on the patch and how validation warnings surface are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The settings object is effectively freeform in the schema (additionalProperties: {} with no inner descriptions), so the description carries the real documentation burden and does so thoroughly — enumerating condition types, image sub-fields with index ranges (characterIndex 0-7, pattern 0-2), movement type enums, speed 1-6, frequency 1-5, priority and trigger enumerations, and the null-disables rule. This is meaning the schema does not supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Patch page settings") and then enumerates exactly which settings — conditions, image, movement, booleans, priority, trigger — so an agent knows the operation's surface precisely. It does not differentiate itself from nearby siblings such as update_map_event or append_event_blocks, but the resource scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear operational context: the tool previews first and returns a change set, and apply=true commits when the preview is clean. It stops short of naming alternatives or exclusions, but the preview/commit contract gives an agent a concrete usage path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server