Skip to main content
Glama
chrischall

zola-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_event_guests

DestructiveIdempotent

Set invitation status for multiple guest groups on an event: invite or uninvite entire groups; uninviting removes associated RSVPs and requires confirmation.

Instructions

Set which guest groups are invited to an event (bulk). For each group, invited:true ensures every guest in the group is invited to the event; invited:false removes the invitation — and with it any RSVP the guest recorded for this event (response, meal choice), which cannot be restored. Other events’ invitations are preserved. Idempotent. Use this to assign guests to events in bulk (e.g. by tier/affiliation/location). A call that uninvites anyone asks the user to confirm first (a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds — see MCP_CONFIRM_MODE). A call that only invites runs immediately.

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent entity ID from list_events (event_entity_id)
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
guest_groupsYesGuest groups to set for this event. Only the listed groups are affected; list each guest_group_id once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.11
    • changedInput schema / properties / guest_groups / description
      Previous value: -"Guest groups to set for this event. Only the listed groups are affected."New value: +"Guest groups to set for this event. Only the listed groups are affected; list each guest_group_id once."
  2. Changed1 schema field changedv2.1.4
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  3. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observedv1.4.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint/idempotentHint/openWorldHint, yet the description adds substantial context beyond them: exactly what is destroyed (RSVP response, meal choice), that it cannot be restored, that other events' invitations are preserved, and the full confirmation protocol including the confirmToken fallback and MCP_CONFIRM_MODE.

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?

Front-loaded with the purpose, then the invited:true/false semantics, then the confirmation mechanics. It is a dense paragraph with one slightly insider reference (MCP_CONFIRM_MODE) but every sentence carries actionable meaning, so no serious padding.

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

Completeness5/5

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

For a destructive bulk mutation with no output schema, the definition covers the safety profile, irreversibility, idempotency, scope preservation, and the two-phase response shape (preview + confirmToken). An agent has everything needed to call it correctly and safely.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes past the schema by spelling out the consequence of invited:false (removes the invitation and any RSVP) and clarifying that only listed groups are affected — meaning that genuinely supplements the field-level 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?

States a specific verb and resource with scope: 'Set which guest groups are invited to an event (bulk)'. The 'guest groups' + 'bulk' framing implicitly separates it from the single-guest sibling invite_guest_to_event and from set_card_project_guests, and the follow-up 'assign guests to events in bulk (e.g. by tier/affiliation/location)' reinforces the scope.

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?

Gives clear usage context (bulk assignment by tier/affiliation/location) and distinguishes invite-only calls (run immediately) from uninvite calls (require confirmation). It never names a sibling alternative such as invite_guest_to_event, so the 'when to use this vs. X' routing is left to inference, keeping it below a 5.

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

Deploy Server

Other Tools