Lemonvite

Create a Lemonvite invitation

lemonvite_create_invitation

Use this when the user wants an actual Lemonvite invitation or RSVP page for an event, party, celebration or gathering: create an invitation, make an invite, set up RSVPs, or use an invitation image created or selected in this conversation (pass it as invitation_image). It creates a DRAFT only and does not publish, charge, or contact anyone. Do not call it merely because invitation wording or images are being discussed. Required: title, event_type, start_datetime, timezone and, for in-person events, location_name (a venue name; the address is optional). Everything else can be added later with lemonvite_update_invitation. If a required detail is missing or invalid, nothing is created and the error names the field to ask the user about. Next steps: lemonvite_add_guests to invite people, then lemonvite_publish_invitation to go live (lemonvite_start_checkout first if payment_status is payment_required).

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Event title, max 60 characters
`timezone`	Yes	IANA timezone of the event's venue (e.g. America/New_York). Required — ask the user if unknown; the wall-clock times are interpreted in this timezone.
`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`	Yes	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.
`reminder_date`	No	Optional: a date (local wall-clock ISO-8601, no offset) on which Lemonvite emails the HOST a reminder about this event — e.g. a year ahead to plan the next one. Never sent to guests; not editable later. Needs an email address on the Lemonvite account.
`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`	Yes	Event start as the venue's LOCAL wall-clock time, ISO-8601 with NO UTC offset
`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_type / description

Added value: +"One of: birthday, wedding, party, baby-shower, celebration-of-life, general. Use 'general' when unsure."

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?

The description adds high-value behavior beyond the annotations: 'It creates a DRAFT only and does not publish, charge, or contact anyone.' It also discloses failure behavior ('nothing is created and the error names the field'), which is important for an agent deciding how to recover. This is genuinely useful context that the plain boolean hints do not provide.

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 dense but every sentence earns its place: trigger condition, draft-only caveat, negative trigger, required fields, error behavior, and next steps all flow in a logical order. No filler or redundant restatement of the schema.

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?

Given the rich schema and output schema, the description covers everything an agent needs to decide when to call the tool, what minimal fields to provide, what failure looks like, and what to do afterward. The only remaining details belong to the schema itself, which is appropriately left there.

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. The description adds value by identifying the minimal required parameter set, calling out the conditional requirement for location_name on in-person events, and explaining how to map a conversation image to invitation_image. This is meaningful guidance for a 26-parameter tool, though the schema already does most of the semantic work.

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 states a specific verb and resource: creating an actual Lemonvite invitation/RSVP page, and lists concrete triggers ('create an invitation, make an invite, set up RSVPs'). It also distinguishes itself from related work by warning 'Do not call it merely because invitation wording or images are being discussed' and by pointing to lemonvite_update_invitation, lemonvite_add_guests, and lemonvite_publish_invitation for later steps.

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?

It explicitly says when to use the tool ('when the user wants an actual Lemonvite invitation or RSVP page'), when not to use it ('merely because invitation wording or images are being discussed'), and names the sibling alternatives for follow-up actions. It also gives a clear next-step sequence: add guests, publish, and checkout when payment is required.

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?