VRChat MCP

Overview Schema Source Related Servers Discussions Admin

vrchat_event_update

Edit an existing VRChat group calendar event, changing details like title, time, or tags. Recurring occurrences and series require a targetKind value.

Instructions

Edit the specified event. Recurring targets require targetKind.

Input Schema

TableJSON Schema

Name	Required	Description
`tags`	No
`title`	No
`endsAt`	No
`groupId`	Yes
`imageId`	No
`isDraft`	No
`roleIds`	No
`category`	No
`featured`	No
`parentId`	No
`startsAt`	No
`languages`	No
`platforms`	No
`calendarId`	Yes
`recurrence`	No
`targetKind`	No	Required for a recurring occurrence or parent series.
`description`	No
`occurrenceKind`	No
`hostEarlyJoinMinutes`	No
`usesInstanceOverflow`	No
`guestEarlyJoinMinutes`	No
`sendCreationNotification`	No
`closeInstanceAfterEndMinutes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`event`	No
`result`	No
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.15Sep 11, 2026

addedInput schema / properties / occurrenceKind
```
Added value: +{
+  "not": {}
+}
```

addedInput schema / properties / recurrence

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "daysOfWeek": {
+          "items": {
+            "enum": [
+              "FR",
+              "MO",
+              "SA",
+              "SU",
+              "TH",
+              "TU",
+              "WE"
+            ],
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "end": {
+          "additionalProperties": {},
+          "properties": {
+            "count": {
+              "maximum": 9007199254740991,
+              "minimum": 1,
+              "type": "integer"
+            },
+            "date": {
+              "type": "string"
+            },
+            "type": {
+              "default": "afterDate",
+              "enum": [
+                "afterDate",
+                "afterOccurrences"
+              ],
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "frequency": {
+          "default": "weekly",
+          "enum": [
+            "daily",
+            "monthly",
+            "weekly",
+            "yearly"
+          ],
+          "type": "string"
+        },
+        "interval": {
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "timezone": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "interval",
+        "timezone"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / targetKind

Added value: +{
+  "description": "Required for a recurring occurrence or parent series.",
+  "enum": [
+    "single_event",
+    "occurrence",
+    "series"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedv0.1.13Sep 6, 2026

changedInput schema / properties / endsAt / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

changedInput schema / properties / startsAt / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

First observedv0.1.8Jul 29, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations supply only readOnlyHint=false, confirming a mutation, so the description carries the rest of the burden and largely fails. It does not mention permission requirements, whether unspecified fields are overwritten or preserved, or side effects like notifications (sendCreationNotification exists in the schema).

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

Conciseness4/5

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

Two short, front-loaded sentences with no filler, so nothing is wasted. The brevity comes at the cost of coverage, but on this dimension alone the structure is efficient.

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

Completeness2/5

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

For a 23-parameter mutation tool with a nested recurrence object, an output schema, and near-zero schema description coverage, two sentences are far short of what an agent needs. It omits update semantics, required identity fields beyond the schema's required list, and any interaction between recurrence and targetKind.

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

Parameters2/5

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

With 23 parameters at 4% schema description coverage, the description must compensate and barely does. Its single parameter note (targetKind needed for recurring targets) just restates the targetKind schema description, leaving title, recurrence, platform, timing, and the other ~20 fields unexplained.

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 ('Edit') and resource ('event'), which cleanly separates it from siblings like vrchat_event_create and vrchat_event_delete. However, it says 'the specified event' while the schema requires groupId and calendarId, not an event id, so the identification story is slightly fuzzy.

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

Usage Guidelines2/5

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

The only guidance is a conditional requirement for recurring targets; there is no statement of when to prefer this over vrchat_event_create, vrchat_event_delete, or the various group-event read tools. An agent must infer that this is the mutation path for an existing event.

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

Deploy Server