Skip to main content
Glama

vrchat_group_post_update

Update a VRChat group post by editing its title, text, image, roles, and visibility. Omitted fields are preserved, with optional member notification.

Instructions

Update a group post. Omitted fields keep their current values; pass roleIds: [] to clear role restrictions. VRChat replaces the whole post on edit, so this reads the most recent 300 posts to recover the fields you did not send. If the post is older than that window, supplying title, text, and visibility still lets the edit land, but it cannot preserve roleIds or imageId and the response reports mergedFromExisting: false. Editing does not re-notify members unless sendNotification is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoPost body text.
titleNoPost title.
postIdYesPost ID from vrchat_group_post_create or vrchat_group_posts_recent. Shaped like a notification ID (not_...).
groupIdNoExact group ID. Provide groupId or shortCode.
imageIdNoReplace the post image. Omit to keep the current image; pass null to remove it.
roleIdsNoReplace the post role restrictions. Omit to keep the current roles; pass an empty array to clear them.
shortCodeNoExact group short code. Provide groupId or shortCode.
visibilityNogroup restricts the post to members; public shows it on the group page.
sendNotificationNoRe-notify group members about the edit. Defaults to false so corrections stay quiet.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
postNo
postIdNo
statusYes
groupIdYes
mergedFromExistingNo
Behavior5/5

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

The description goes well beyond the minimal readOnlyHint: false annotation. It discloses that the tool replaces the whole post, reads the most recent 300 posts to recover omitted fields, cannot preserve roleIds/imageId for older posts, and reports mergedFromExisting: false in that case. It also explains that notifications are only sent when sendNotification is true. This is rich, non-obvious behavioral context.

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

Conciseness5/5

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

The description is three dense sentences, each earning its place: update semantics, recovery mechanism with edge case, and notification behavior. It is front-loaded with the purpose and contains no filler.

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?

The description covers the tool's key behavioral complexity: partial updates, old-post fallback, and notification control, while referencing an output field (mergedFromExisting). It does not discuss error cases or permissions, but given the output schema exists and the annotations provide safety info, it is sufficiently complete for an AI agent.

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

Parameters4/5

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

The input schema already covers all 9 parameters with 100% description coverage, so baseline is 3. The description adds cross-parameter meaning: omitted fields keep current values, roleIds: [] clears restrictions, and the 300-post window affects which fields can be preserved. This goes beyond the individual schema descriptions.

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

Purpose5/5

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

The description opens with 'Update a group post,' a specific verb+resource that clearly distinguishes this from sibling tools like create/delete. It also specifies the update semantics (omitted fields keep current values), making the tool's purpose unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the tool name and the verb 'Update,' and the description gives clear context for the operation. However, it does not explicitly contrast with alternatives like vrchat_group_post_create/delete or state when not to use this tool, so the guidance is implied rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BASIC-BIT/vrchat-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server