Luma

Create a tag for grouping events on a calendar you manage, such as “Workshops” or “Meetups”. Visitors can filter the calendar page by tag. Tag names are unique per calendar. Apply it with `apply_calendar_event_tag`. Returns the calendar's event tags.

create_calendar_event_tag

Create a coupon code that guests enter when registering. Pass `event_id` for one event, or `calendar_id` for a code that works on every event on the calendar; an event's own coupon with the same code takes priority. The discount is a percent, or a fixed amount in the currency's smallest unit (cents for USD). Pass `ticket_type_id` (event coupons only) to limit it to one ticket type; if that type is hidden, the code unlocks it, and `percent_off: 0` makes an unlock code that keeps the price. Unlimited uses unless you pass `remaining_count`. Codes are case-insensitive and must be unique on the event or calendar. The code, discount, and ticket type can't be changed later. Returns the coupon.

create_coupon

Create an event on a calendar you manage (see `list_calendars`). Events are public by default; pass `visibility` to change this. Queues a confirmation email to the host. For in-person venues, prefer `geo_address_json: { type: 'lookup', query }`; unmatched addresses are stored as text. Use `search_places` first for ambiguous venues. For online events, pass `meeting_url`, or `create_meeting` to have Luma create a Zoom or Google Meet link. Omit all location fields for location TBD. Require registration approval with `ticket_types[].require_approval: true`. Pass `registration_questions` to collect answers at registration; see `add_registration_question` for question types. Returns the `get_event` manage view, including the event URL.

create_event

Add a ticket type to an event you manage. Returns the new ticket type.

create_ticket_type

Delete a blast on an event you manage. Deleting a scheduled blast cancels the send. Deleting a sent blast removes the post from the event page, but the emails already delivered stay delivered. Confirm with the user first.

delete_blast

Delete a contact tag on a calendar you manage and take it off every contact that has it. The contacts themselves stay. Confirm with the user first. Returns the calendar's remaining contact tags.

delete_calendar_contact_tag

Delete an event tag on a calendar you manage and take it off every event that has it. The events themselves stay on the calendar. Confirm with the user first. Returns the calendar's remaining event tags.

delete_calendar_event_tag

Delete a registration question from an event you manage. Guests' existing answers are preserved and remain visible in guest details. Confirm with the user first when the event has registrations.

delete_registration_question

Delete a ticket type from an event you manage. Guests already registered with it keep their tickets, so confirm with the user first when the type has registrations. Fails if it's the event's last visible ticket type.

delete_ticket_type

Get information about a calendar that you have manage access for.

get_calendar

Get information for an event, scoped to your role. Managers get full settings (`view: 'manage'`): the description as `description_md` markdown, hosts with contact info, `ticket_types`, `registration_questions` (with the IDs the question tools take), and `guest_counts` by status. Guests, invitees, and non-manager hosts get the guest-facing event summary (`view: 'guest'`), with location and meeting details once approved. Public events can be looked up by anyone (`view: 'public'`); private events you have no connection to return not found.

get_event

Get detailed information for a guest on an event you manage, including contact information, registration answers, check-in code, tickets, and order and refund amounts. `id` can be the guest ID (gst-), ticket key, guest key (g-), or the user's email.

get_guest

Get the authenticated user (the Luma account whose OAuth token is in use), including their public profile: username, bio, website, and social handles.

get_self

Add up to 500 people to the contacts of a calendar you manage, by email, so you can invite them to events and send them newsletters. Nobody is emailed. Imports run in the background and count against the calendar's import limit; people who are already contacts don't count, so re-importing them is a way to tag them in bulk. Existing Luma users keep their own name. Optionally tag everyone in the import with existing contact tags (see `list_calendar_contact_tags`).

import_calendar_contacts

Email invites to up to 100 guests for an event you manage. Sends run in the background and count against the calendar's send limit. Existing invitees and registrants are skipped; unsubscribed people and those blocking the host are also skipped and listed under `skipped`. Resolve names without emails through `search_people` first, asking the user to disambiguate plausible matches before inviting.

invite_guests

List the blasts (emails to guests) on an event you manage, newest first. Each has the message as `content_md` markdown, its audience as `recipient_groups`, and for sent blasts the `recipient_count` and `email_open_count`. `status` is `scheduled` until the send finishes, then `sent`; `quarantined` means it's held for review. `can_reschedule` is true until a blast is sent.

list_blasts

List the direct admins of a calendar you manage. Admins of the calendar's organization also manage it but aren't listed here; see `list_organization_admins`.

list_calendar_admins

List the tags used to organize contacts on a calendar you manage. Returns tag IDs, names, and colors. Use the IDs or names to filter `list_calendar_contacts`.

list_calendar_contact_tags

List or search the audience of a calendar you manage, without needing an event. Returns names, emails, tags, registration and check-in counts, revenue in USD cents, and membership details. Search by name or email; filter by tag names or IDs (matching any tag), membership tier, or membership status. Use `list_calendar_contact_tags` to find available tags. Sort by join date (`created_at`, the default), name, registrations (`event_approved_count`), check-ins (`event_checked_in_count`), or revenue. Always sorted descending: newest first for join date, highest first for counts and revenue, Z–A for names. Paginated.

list_calendar_contacts

List the tags used to group events on a calendar you manage. Returns tag IDs, names, and colors. `list_calendar_events` shows each event's tags by name.

list_calendar_event_tags

List events on a calendar you manage (see `list_calendars`), including events you don't host. Upcoming events sort soonest-first; past events newest-first. `platform: 'luma'` entries are Luma events: `access: 'manage'` permits editing; `access: 'view'` means listed events managed elsewhere, with city-level locations. Pending submissions have `access: 'view'` until approved. Use `get_event` for full details. `platform: 'external'` entries are listings for events hosted off Luma: `url` links to the event elsewhere and `host` is free text. They have no `access`, and the event tools (`get_event`, `update_event`, guests) don't apply; only `approve_calendar_events` / `reject_calendar_events` apply while pending, and `remove_calendar_events` once approved. Paginated.

list_calendar_events

List calendars you manage — as a direct admin or through an organization you admin. Sorted by name. Returns the same calendar shape as `get_calendar`.

list_calendars

List the coupons on an event or calendar you manage, sorted by code. Pass exactly one of `event_id` or `calendar_id`. Calendar coupons work on every event on the calendar but aren't listed under an event. A `remaining_count` of 1000000 means unlimited, and 0 means used up or invalidated. `ticket_type_id` is set when the coupon only applies to that ticket type. Paginated.

list_coupons

List guests registered or invited to an event you manage, including contact information, registration answers, check-in codes, and `event_tickets`. Use `get_guest` for a single guest's order and refund amounts in `event_ticket_orders`. Paginated.

list_guests

List the admins of an organization you admin (see `list_organizations`). Organization admins manage every calendar in the organization.

list_organization_admins

List the calendars in an organization you admin (see `list_organizations`). Sorted by name. Returns the same calendar shape as `get_calendar`. Paginated.

list_organization_calendars

List organizations you admin. Organizations group team calendars under one plan. Use an `id` with `list_organization_calendars`, `list_organization_admins`, or `add_calendar_to_organization`.

list_organizations

List upcoming pending event submissions across every calendar you manage (see `list_calendars`), soonest first, so you can find the queues that need review without checking each calendar. Pass `organization_id` (see `list_organizations`) to only include that organization's calendars. Each entry has the same shape as `list_calendar_events` with `status: 'pending'`, plus the `calendar` it was submitted to. Approve or reject with `approve_calendar_events` / `reject_calendar_events` using that calendar's `id`. Paginated.

list_pending_calendar_events

List events you're hosting or attending, with your relationship and accessible location or meeting details. Upcoming events sort soonest-first; past events newest-first. Use `get_event` for full details. Paginated.

list_events

Resolve a Luma URL (luma.com or lu.ma) or slug to an event or calendar's type, ID, and basic details. Use shared links here first, then pass the ID to other tools. Private links expose only basic metadata, not guest lists, private locations, or management access. Returns `entity: null` if unmatched; this is not a slug availability check.

lookup_entity

Reject up to 50 pending event submissions on a calendar you manage. Find submissions with `list_calendar_events` using `status: 'pending'`, then pass their `id`s. Submitters aren't emailed unless you pass `notify_submitter: true` or a plain-text `message` explaining the rejection, which is sent to every submitter in the call. Only pending submissions can be rejected; to take an already-approved event off the calendar, use `remove_calendar_events`. This does not cancel the underlying events. Each ID succeeds or fails on its own; failures are listed under `errors`.

reject_calendar_events

Remove admins from a calendar you manage, by email (see `list_calendar_admins`). This removes only the direct admin role: organization admins keep managing the calendar through the organization (see `list_organization_admins`). On a Luma Plus calendar, the paid admin seat count shrinks to match. Every email must belong to a current admin, and at least one admin must remain. Returns the calendar's admins after the removal.

remove_calendar_admins

Remove up to 50 approved events from a calendar you manage, the same as removing them from the calendar dashboard. Find them with `list_calendar_events`, then pass their `id`s. Removed events no longer appear on the calendar, their calendar tags are cleared, and any management access the calendar had through the listing is revoked. Submitters are not notified, and the underlying events are not cancelled or changed. Events the calendar hosts itself can't be removed; hide them with `update_event` (`visibility`) or cancel them instead. For pending submissions, use `reject_calendar_events`. Each ID succeeds or fails on its own; failures are listed under `errors`.

remove_calendar_events

Remove a host from an event you manage, by email (see `hosts` on `get_event`). The event creator can't be removed. Returns the event's remaining hosts.

remove_host

Remove admins from an organization you admin, by email (see `list_organization_admins`). This removes only the organization admin role: anyone who is also a direct admin of one of its calendars keeps that access (see `list_calendar_admins`). Every email must belong to a current admin, and at least one admin must remain. Returns the organization's admins after the removal.

remove_organization_admins

Change the order guests see the registration questions in on an event you manage. Pass every question's ID from `registration_questions` on `get_event`, in the new order; a list that skips or repeats a question is rejected. Guests' existing answers stay attached. Returns the reordered questions.

reorder_registration_questions

Search Luma’s gallery of stock event cover images by keyword, e.g. “dinner party” or “hackathon”. Each result has an `image_url` to pass as `cover_url` to `create_event` or `update_event`, plus a description, tags, and dominant colors to help pick one that fits the event.

search_cover_images

Find people to invite to an event you manage, limited to members of calendars you admin and imported contacts, ranked by connection strength. Includes this event's `approval_status` and `invited_at`. Ask the user before inviting if multiple people plausibly match or the top match is unclear; ranking doesn't prove identity. Results without `email` can't be invited through `invite_guests`. Paginated.

search_people

Search Google Maps for a venue or address and get up to 5 candidates. Use it to confirm the right place with the user before creating or updating an event, then pass the chosen `place_id` as `geo_address_json: { type: 'google', place_id }`. Skip it when the address is unambiguous — `geo_address_json: { type: 'lookup', query }` resolves the top result directly.

search_places

Search upcoming public events on Luma by keyword. Pass `location` (free text, geocoded server-side) to return only events in that area — an empty result means nothing matched there, so retry without `location` for worldwide matches. Or pass `latitude`/`longitude` to rank events near that point first, followed by matches from elsewhere. Narrow to a time window with `after`/`before` (filtering on event start time) — only upcoming events are searchable. Returns a single ranked page of concise event summaries with any location or meeting details available to you.

search_events