Lemonvite

Update an invitation

lemonvite_update_invitation

DestructiveIdempotent

Use this when the user asks to change a saved Lemonvite invitation: its title, description, date and time, location, host details, RSVP and guest settings, custom fields, or artwork (pass a new invitation_image). Only the fields you pass change; omitted fields keep their saved values. Read the current values with lemonvite_get_invitation first, especially before changing custom_fields: that list replaces the saved one, and a saved field left out is deleted with its guest answers. On a published invitation the public RSVP page shows the change on its next load, and guests are not notified. Do not call it merely to discuss possible changes. To create a new event use lemonvite_create_invitation; for new artwork from the design engine use lemonvite_generate_design or lemonvite_edit_design; to go live use lemonvite_publish_invitation.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Event title, max 60 characters
`event_id`	Yes	Lemonvite event_id returned by lemonvite_create_invitation or lemonvite_list_invitations. Identifies the event to act on; not a guest invitation_id or RSVP URL.
`timezone`	No	IANA timezone, e.g. America/New_York
`host_name`	No	Host name shown on the invitation ("from …"). Defaults to the account's display name — required at create when the account has none (e.g. phone-only signups).
`event_type`	No	One of: birthday, wedding, party, baby-shower, celebration-of-life, general. Use 'general' when unsure.
`is_virtual`	No	True for an online event using virtual_url; false for an in-person event requiring location_name. Defaults to false on create.
`max_guests`	No	Event capacity — the most guests that can RSVP yes. null = uncapped.
`description`	No	Invitation wording/details shown to guests
`virtual_url`	No	Meeting URL for virtual events
`end_datetime`	No	Event end, local wall-clock ISO-8601 with no UTC offset. Pass null to remove an existing end time.
`custom_fields`	No	The host's custom fields — the COMPLETE list, in display order, replacing what is saved. Two kinds: `info` = a detail shown on the invitation for guests to read (gift registry link, dress code, parking); `question` = an input on the RSVP form guests answer when they say yes or maybe (dietary restrictions, meal choice), optionally required. To edit, read custom_fields from lemonvite_get_invitation, change the list and send it back WITH each existing field_id — a field sent without its field_id is created anew and a saved field left out of the list is deleted together with any guest answers. Omit to leave the fields unchanged; pass [] to remove them all. Up to 10 of each kind.
`location_name`	No	Venue name — REQUIRED for in-person events (anything that tells guests where: "Central Park", "Our place"). Ask the user if you do not know it. Not needed when is_virtual is true.
`rsvp_deadline`	No	RSVP-by date, local wall-clock ISO-8601 with no UTC offset (must be before start_datetime). Pass null to remove an existing deadline.
`start_datetime`	No	Event start as the venue's LOCAL wall-clock time, ISO-8601 with NO UTC offset (e.g. 2026-10-04T18:00:00)
`allow_plus_ones`	No	Whether guests may bring additional attendees, subject to the adult and child limits. Defaults to true on create.
`group_chat_link`	No	URL of a group chat for guests (WhatsApp, Signal, …), shown on the invitation. Pass null to clear.
`show_guest_list`	No	Whether guests can see who else is invited
`invitation_image`	No	An invitation graphic already present in this conversation (for example an image the assistant generated). Lemonvite downloads and stores it permanently as the invitation artwork.
`location_address`	No	Street address of the venue (optional; helps guests find it). Never required.
`allow_guest_posts`	No	Whether guests may post on the event wall (default true)
`guest_bring_items`	No	What guests should bring, shown on the invitation. Pass null to clear.
`default_limit_kids`	No	Default plus-one allowance: how many KIDS each guest may bring (0–20). null = no limit.
`allow_guest_replies`	No	Whether guests may reply to wall posts (default true)
`birthday_person_name`	No	Name of the person being celebrated at a birthday event, up to 120 characters.
`default_limit_adults`	No	Default plus-one allowance: how many ADULTS each guest may bring (0–20). null = no limit. Both limits at 0 is refused.
`birthday_person_likes`	No	Gift and interest hints for the birthday person (birthday events). Pass null to clear.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`warnings`	No
`invitation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

changedOutput schema / properties / invitation / properties / payment_status / description

Previous value: -"paid = this event is already covered; credit_available = balance covers all required publishing and phone credits; payment_required = start_checkout first; not_applicable = cancelled, do not buy credits or publish. Always reflects the PRIMARY host's account — the one publishing charges."New value: +"paid = this event is already covered; credit_available = balance covers all required publishing and phone credits; payment_required = the account's credits do not cover publishing; not_applicable = cancelled, cannot be published. Always reflects the PRIMARY host's account — the one whose credits publishing uses."

changedOutput schema / properties / invitation / properties / phone_guest_allowance / description

Previous value: -"Included or already purchased phone guests; null = no phone cap."New value: +"Phone guests this event already allows; null = no phone cap."

Changed10 schema fields changedSep 21, 2026

changedOutput schema / properties / invitation / properties / can_publish / description

Previous value: -"True when this account is the event's primary host — the only account that can publish it or pay for it. Co-hosts can edit the invitation and manage guests, but must ask the primary host to publish."New value: +"True when this account is the event's primary host and the event is not cancelled. Co-hosts can edit the invitation and manage guests, but must ask the primary host to publish."

addedOutput schema / properties / invitation / properties / guest_limit

Added value: +{
+  "description": "Total cap; only support can raise it. null = verified host.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

changedOutput schema / properties / invitation / properties / payment_status / description

Previous value: -"paid = this event is already covered; credit_available = publish will consume an existing credit; payment_required = start_checkout first. Always reflects the PRIMARY host's account — the one publishing charges."New value: +"paid = this event is already covered; credit_available = balance covers all required publishing and phone credits; payment_required = start_checkout first; not_applicable = cancelled, do not buy credits or publish. Always reflects the PRIMARY host's account — the one publishing charges."

changedOutput schema / properties / invitation / properties / payment_status / enum

Previous value: -[
-  "paid",
-  "credit_available",
-  "payment_required"
-]New value: +[
+  "paid",
+  "credit_available",
+  "payment_required",
+  "not_applicable"
+]

addedOutput schema / properties / invitation / properties / phone_batch_size
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

addedOutput schema / properties / invitation / properties / phone_guest_allowance

Added value: +{
+  "description": "Included or already purchased phone guests; null = no phone cap.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / invitation / properties / phone_guest_count
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / invitation / properties / publishing_price

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "amount_due": {
+          "type": "number"
+        },
+        "credits_to_buy": {
+          "type": "number"
+        },
+        "existing_credits": {
+          "type": "number"
+        },
+        "phone_batch_count": {
+          "type": "number"
+        },
+        "phone_batch_price": {
+          "type": "number"
+        },
+        "publish_price": {
+          "type": "number"
+        },
+        "total_price": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "publish_price",
+        "phone_batch_count",
+        "phone_batch_price",
+        "total_price",
+        "existing_credits",
+        "credits_to_buy",
+        "amount_due"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / invitation / properties / required_credits

Added value: +{
+  "description": "Publishing plus phone batches. Review with the host before authorizing this many credits.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

changedOutput schema / properties / invitation / required

Previous value: -[
-  "event_id",
-  "publish_status",
-  "payment_status",
-  "can_publish",
-  "title",
-  "event_type",
-  "description",
-  "start_datetime",
-  "end_datetime",
-  "timezone",
-  "location",
-  "host_name",
-  "rsvp_deadline",
-  "image_url",
-  "has_invitation_image",
-  "price_display",
-  "guest_count",
-  "rsvp_summary",
-  "public_rsvp_url",
-  "manage_url",
-  "custom_fields",
-  "guest_settings"
-]New value: +[
+  "event_id",
+  "publish_status",
+  "payment_status",
+  "can_publish",
+  "title",
+  "event_type",
+  "description",
+  "start_datetime",
+  "end_datetime",
+  "timezone",
+  "location",
+  "host_name",
+  "rsvp_deadline",
+  "image_url",
+  "has_invitation_image",
+  "price_display",
+  "guest_count",
+  "phone_guest_count",
+  "guest_limit",
+  "phone_guest_allowance",
+  "phone_batch_size",
+  "required_credits",
+  "publishing_price",
+  "rsvp_summary",
+  "public_rsvp_url",
+  "manage_url",
+  "custom_fields",
+  "guest_settings"
+]

Changed8 schema fields changedSep 10, 2026

addedInput schema / properties / allow_plus_ones / description

Added value: +"Whether guests may bring additional attendees, subject to the adult and child limits. Defaults to true on create."

addedInput schema / properties / birthday_person_name / description

Added value: +"Name of the person being celebrated at a birthday event, up to 120 characters."

addedInput schema / properties / event_id / description

Added value: +"Lemonvite event_id returned by lemonvite_create_invitation or lemonvite_list_invitations. Identifies the event to act on; not a guest invitation_id or RSVP URL."

changedInput schema / properties / invitation_image / properties / download_url / description

Previous value: -"Temporary URL to download the file from"New value: +"Fetchable HTTPS URL for the image file, up to 10 MB. Temporary conversation-file URLs are accepted."

changedInput schema / properties / invitation_image / properties / file_id / description

Previous value: -"Host file identifier"New value: +"File identifier supplied by the MCP client for the image in this conversation."

addedInput schema / properties / invitation_image / properties / file_name / description

Added value: +"Original filename, e.g. invitation.png. Optional metadata; the stored filename is generated by Lemonvite."

addedInput schema / properties / invitation_image / properties / mime_type / description

Added value: +"Image MIME type: image/jpeg, image/png, image/webp, or image/gif. Design references exclude GIF. Used if the download has no Content-Type."

addedInput schema / properties / is_virtual / description

Added value: +"True for an online event using virtual_url; false for an in-person event requiring location_name. Defaults to false on create."

Changed3 schema fields changedSep 10, 2026

addedInput schema / properties / custom_fields

Added value: +{
+  "description": "The host's custom fields — the COMPLETE list, in display order, replacing what is saved. Two kinds: `info` = a detail shown on the invitation for guests to read (gift registry link, dress code, parking); `question` = an input on the RSVP form guests answer when they say yes or maybe (dietary restrictions, meal choice), optionally required. To edit, read custom_fields from lemonvite_get_invitation, change the list and send it back WITH each existing field_id — a field sent without its field_id is created anew and a saved field left out of the list is deleted together with any guest answers. Omit to leave the fields unchanged; pass [] to remove them all. Up to 10 of each kind.",
+  "items": {
+    "properties": {
+      "field_id": {
+        "description": "The saved field this entry updates (from lemonvite_get_invitation). Omit for a new field.",
+        "type": "string"
+      },
+      "input_type": {
+        "description": "question only: text (free answer, default) or select (guest picks one of `options`).",
+        "enum": [
+          "text",
+          "select"
+        ],
+        "type": "string"
+      },
+      "kind": {
+        "description": "info = shown on the invitation; question = asked on the RSVP form.",
+        "enum": [
+          "info",
+          "question"
+        ],
+        "type": "string"
+      },
+      "label": {
+        "description": "The heading guests see (\"Gift registry\", \"Any dietary restrictions?\").",
+        "maxLength": 80,
+        "type": "string"
+      },
+      "options": {
+        "description": "select questions only: 2 or more distinct choices.",
+        "items": {
+          "maxLength": 60,
+          "type": "string"
+        },
+        "maxItems": 12,
+        "type": "array"
+      },
+      "required": {
+        "description": "question only: guests saying yes or maybe must answer (default false).",
+        "type": "boolean"
+      },
+      "value": {
+        "description": "info only, required for that kind: the text shown under the heading. URLs become links.",
+        "maxLength": 1000,
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "label"
+    ],
+    "type": "object"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedOutput schema / properties / invitation / properties / custom_fields

Added value: +{
+  "description": "The host's custom fields, in display order: `info` details shown on the invitation (gift registry, dress code) and `question` inputs on the RSVP form (dietary restrictions, meal choice). Change them with custom_fields on lemonvite_update_invitation.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "field_id": {
+        "type": "string"
+      },
+      "input_type": {
+        "anyOf": [
+          {
+            "enum": [
+              "text",
+              "select"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "question fields only."
+      },
+      "kind": {
+        "enum": [
+          "info",
+          "question"
+        ],
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "options": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "select questions only: the choices offered."
+      },
+      "required": {
+        "description": "question fields only: must be answered by a guest who says yes or maybe.",
+        "type": "boolean"
+      },
+      "value": {
+        "description": "info fields only: the text shown on the invitation (may contain a URL).",
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "field_id",
+      "kind",
+      "label",
+      "value",
+      "input_type",
+      "options",
+      "required"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / invitation / required

Previous value: -[
-  "event_id",
-  "publish_status",
-  "payment_status",
-  "can_publish",
-  "title",
-  "event_type",
-  "description",
-  "start_datetime",
-  "end_datetime",
-  "timezone",
-  "location",
-  "host_name",
-  "rsvp_deadline",
-  "image_url",
-  "has_invitation_image",
-  "price_display",
-  "guest_count",
-  "rsvp_summary",
-  "public_rsvp_url",
-  "manage_url",
-  "guest_settings"
-]New value: +[
+  "event_id",
+  "publish_status",
+  "payment_status",
+  "can_publish",
+  "title",
+  "event_type",
+  "description",
+  "start_datetime",
+  "end_datetime",
+  "timezone",
+  "location",
+  "host_name",
+  "rsvp_deadline",
+  "image_url",
+  "has_invitation_image",
+  "price_display",
+  "guest_count",
+  "rsvp_summary",
+  "public_rsvp_url",
+  "manage_url",
+  "custom_fields",
+  "guest_settings"
+]

First observedSep 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds crucial behavioral context beyond those flags: partial-update semantics (omitted fields keep saved values), the destructive replace behavior of custom_fields (a saved field left out is deleted with its guest answers), the fact that published invitations update on next page load without notifying guests, and the requirement to pass existing field_ids. This is rich, non-obvious behavioral disclosure that materially changes how an agent should call the tool.

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 a single dense paragraph that front-loads the core purpose and usage condition, then packs the most important behavioral warnings (partial update, custom_fields replacement, published page behavior) before the sibling routing. Every sentence earns its place; there is no filler or repetition of schema content.

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 26-parameter mutation tool with a full output schema and 100% schema description coverage, the description covers the essential operational context: when to use it, what changes, what doesn't, the destructive custom_fields behavior, published-invitation visibility, and which siblings handle other intents. The output schema exists, so return values need no explanation. Nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the overall partial-update model ('Only the fields you pass change; omitted fields keep their saved values') and by highlighting the custom_fields replace semantics and the need to read current values first. It also clarifies the invitation_image parameter as 'pass a new invitation_image' for artwork changes. The description doesn't enumerate every parameter, but the schema already covers them thoroughly, so the added semantic layer is meaningful.

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 a specific verb and resource ('change a saved Lemonvite invitation') and enumerates exactly which fields can be changed, including artwork via invitation_image. It also distinguishes itself from siblings by naming lemonvite_create_invitation, lemonvite_generate_design, lemonvite_edit_design, and lemonvite_publish_invitation as the tools for other intents. An agent can tell exactly what this tool is for.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance ('Use this when the user asks to change a saved Lemonvite invitation'), tells the agent to read current values with lemonvite_get_invitation first, warns against calling it merely to discuss changes, and names the sibling tools for create, design, and publish. This is exemplary routing guidance.

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

All Lemonvite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?