Skip to main content
Glama

add_guest

Add a guest household to a Zola guest list with an optional plus-one, mailing address, and event invitations, creating a fully set-up household in one call.

Instructions

Add a new guest group (household) to the guest list, optionally with a partner/plus-one, mailing address and event invitations, so one call creates a fully set-up household. Affiliation is relative to the Zola account owner: PRIMARY_* is the account owner's side, PARTNER_* is the other partner's side (the web UI labels PARTNER_* with the partner's name, e.g. "'s Family Friend"). Check list_guests for duplicates first. Guests are invited only to the events in event_ids — none when omitted. Adds to the list only: no invitation, save-the-date or email is sent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "first_name": "<first_name>",
      "last_name": "<last_name>"
    },
    "name": "add_guest"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
tierNoGuest-list tier (default: A)
emailNoPrimary guest email address
phoneNoPrimary guest mobile phone
address1NoStreet address (applied to every guest in the household)
address2No
event_idsNoEvent ids from list_events to invite every guest in the household to. Omit to invite to none.
last_nameYesPrimary guest last (family) name
first_nameYesPrimary guest first name
affiliationNoRelationship to the couple (default PRIMARY_FRIEND). PRIMARY_* = the account owner's side; PARTNER_* = the other partner's side. Known values: PRIMARY_FRIEND, PRIMARY_FAMILY, PRIMARY_FAMILY_FRIEND, PARTNER_FRIEND, PARTNER_FAMILY, PARTNER_FAMILY_FRIEND, BOTH, UNKNOWN. Case-insensitive.
postal_codeNo
country_codeNoDefault: US (only sent with an address)
state_provinceNoState / province code, e.g. FL
plus_one_last_nameNoPartner / plus-one last name (default: the primary guest's last name)
plus_one_first_nameNoPartner / plus-one first name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv2.2.1
    • addedInput schema / properties / address1
      Added value: +{
      +  "description": "Street address (applied to every guest in the household)",
      +  "type": "string"
      +}
    • addedInput schema / properties / address2
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / affiliation / description
      Previous value: -"Affiliation (default: PRIMARY_FRIEND)"New value: +"Relationship to the couple (default PRIMARY_FRIEND). PRIMARY_* = the account owner's side; PARTNER_* = the other partner's side. Known values: PRIMARY_FRIEND, PRIMARY_FAMILY, PRIMARY_FAMILY_FRIEND, PARTNER_FRIEND, PARTNER_FAMILY, PARTNER_FAMILY_FRIEND, BOTH, UNKNOWN. Case-insensitive."
    • addedInput schema / properties / city
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / country_code
      Added value: +{
      +  "description": "Default: US (only sent with an address)",
      +  "type": "string"
      +}
    • changedInput schema / properties / email / description
      Previous value: -"Guest email address"New value: +"Primary guest email address"
    • addedInput schema / properties / event_ids
      Added value: +{
      +  "description": "Event ids from list_events to invite every guest in the household to. Omit to invite to none.",
      +  "items": {
      +    "type": "number"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / first_name / minLength
      Added value: +1
    • changedInput schema / properties / last_name / description
      Previous value: -"Primary guest last name"New value: +"Primary guest last (family) name"
    • addedInput schema / properties / last_name / minLength
      Added value: +1
    • changedInput schema / properties / phone / description
      Previous value: -"Guest phone number"New value: +"Primary guest mobile phone"
    • changedInput schema / properties / plus_one_first_name / description
      Previous value: -"Plus-one first name"New value: +"Partner / plus-one first name"
    • changedInput schema / properties / plus_one_last_name / description
      Previous value: -"Plus-one last name"New value: +"Partner / plus-one last name (default: the primary guest's last name)"
    • addedInput schema / properties / postal_code
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / state_province
      Added value: +{
      +  "description": "State / province code, e.g. FL",
      +  "type": "string"
      +}
    • addedInput schema / properties / tier
      Added value: +{
      +  "description": "Guest-list tier (default: A)",
      +  "type": "string"
      +}
  2. 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"
  3. First observedv1.4.2

TDQS

A4.5/5.0
Behavior5/5

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

Annotations are thin (openWorldHint, destructiveHint=false), so the description carries real weight and does — it discloses the side-effect boundary ("Adds to the list only: no invitation, save-the-date or email is sent") and clarifies that the call creates a full household including a plus-one and shared address. That is exactly the behavior an agent cannot infer from the annotation set, and nothing here contradicts destructiveHint=false.

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?

The purpose is front-loaded in the opening clause, then prerequisites, affiliation semantics and side effects follow in a logical order. It is a dense paragraph of five sentences, but each carries distinct information, with little 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?

For a 15-parameter mutation with no output schema, the description covers the critical unknowns: household scope, event-invitation behavior, and the no-email side effect. It never indicates what is returned (e.g., created guest ids) or how the plus-one and address fields interact with later updates, which are the remaining gaps.

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 80%, so the baseline is 3; the description adds genuine meaning on top by explaining that affiliation is relative to the account owner and how PARTNER_* renders in the web UI ("<partner>'s Family Friend"), plus the household-wide scope of the address and the omission semantics of event_ids. It adds value but leaves several undocumented params (city, address2, postal_code, phone) unaddressed.

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 first sentence names a specific verb and resource ("Add a new guest group (household) to the guest list") and enumerates the optional payload (plus-one, mailing address, event invitations), so the agent can distinguish it from siblings like add_vendor or invite_guest_to_event without opening the schema.

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?

It gives an explicit prerequisite ("Check list_guests for duplicates first") and states the invitation-scoping rule ("Guests are invited only to the events in event_ids — none when omitted"). It stops short of naming the alternative path for inviting an existing guest later (invite_guest_to_event / set_event_guests), so there is clear context but no full alternative routing.

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