You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add and refine tools across Kalshi, Luma, Rootly, Polymarket, Railway,
LaunchDarkly, and Sentry; register all new tools
- Regenerate tool docs to match the updated source
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/tools/launchdarkly.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ List audit log entries from your LaunchDarkly account.
106
106
| --------- | ---- | -------- | ----------- |
107
107
|`apiKey`| string | Yes | LaunchDarkly API key |
108
108
|`limit`| number | No | Maximum number of entries to return \(default 10, max 20\)|
109
-
|`spec`| string | No | Resource specifier filter \(e.g. "resourceType:flag" for all flag changes, or "proj/default:env/production:flag/my-flag" for one flag in one environment\)|
109
+
|`spec`| string | No | Resource specifier filter \(e.g. "proj/*:env/*:flag/*" for all flag changes, or "proj/default:env/production:flag/my-flag" for one flag in one environment\)|
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/tools/luma.mdx
+108-8Lines changed: 108 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Whether you're running community meetups, conferences, or internal team events,
30
30
31
31
## Usage Instructions
32
32
33
-
Integrate Luma into the workflow. Can create events, update events, get event details, list calendar events, get guest lists, and add guests to events.
33
+
Integrate Luma into the workflow. Can create, update, look up, and cancel events, list calendar events, manage guest lists (get one or many, add guests, send invites, and update approval status).
34
34
35
35
36
36
@@ -217,6 +217,47 @@ List events from your Luma calendar with optional date range filtering, sorting,
217
217
|`hasMore`| boolean | Whether more results are available for pagination |
218
218
|`nextCursor`| string | Cursor to pass as paginationCursor to fetch the next page |
219
219
220
+
### `luma_lookup_event`
221
+
222
+
Look up an event by its public URL or event ID to resolve its canonical ID, API ID, and approval status.
223
+
224
+
#### Input
225
+
226
+
| Parameter | Type | Required | Description |
227
+
| --------- | ---- | -------- | ----------- |
228
+
|`apiKey`| string | Yes | Luma API key |
229
+
|`url`| string | No | Public event URL on lu.ma \(provide this or an event ID\)|
230
+
|`eventId`| string | No | Event ID to look up \(starts with evt-\). Provide this or a URL. |
231
+
|`platform`| string | No | Event platform to look up: luma or external \(defaults to luma\)|
232
+
233
+
#### Output
234
+
235
+
| Parameter | Type | Description |
236
+
| --------- | ---- | ----------- |
237
+
|`found`| boolean | Whether a matching event was found |
238
+
|`eventId`| string | Resolved event ID |
239
+
|`apiId`| string | Resolved event API ID \(deprecated identifier\)|
240
+
|`status`| string | Event approval status \(approved, pending, rejected\)|
241
+
242
+
### `luma_cancel_event`
243
+
244
+
Cancel a Luma event. This is irreversible and notifies all registered guests. Requires a cancellation token obtained from the Request Event Cancellation endpoint.
245
+
246
+
#### Input
247
+
248
+
| Parameter | Type | Required | Description |
249
+
| --------- | ---- | -------- | ----------- |
250
+
|`apiKey`| string | Yes | Luma API key |
251
+
|`eventId`| string | Yes | Event ID to cancel \(starts with evt-\)|
252
+
|`cancellationToken`| string | Yes | Cancellation token from the Request Event Cancellation endpoint \(POST /v1/event/cancel/request\)|
253
+
|`shouldRefund`| boolean | No | Whether to refund paid guests. Required if the event has paid registrations. |
254
+
255
+
#### Output
256
+
257
+
| Parameter | Type | Description |
258
+
| --------- | ---- | ----------- |
259
+
|`cancelled`| boolean | Whether the event was successfully cancelled |
260
+
220
261
### `luma_get_guests`
221
262
222
263
Retrieve the guest list for a Luma event with optional filtering by approval status, sorting, and pagination.
@@ -247,28 +288,28 @@ Retrieve the guest list for a Luma event with optional filtering by approval sta
| ↳ `checkedInAt`| string | Check-in timestamp from the first checked-in ticket \(ISO 8601\)|
282
323
| ↳ `phoneNumber`| string | Guest phone number |
283
324
325
+
### `luma_add_guests`
326
+
327
+
Add guests to a Luma event by email. Guests are added with Going (approved) status and receive one ticket of the default ticket type.
328
+
329
+
#### Input
330
+
331
+
| Parameter | Type | Required | Description |
332
+
| --------- | ---- | -------- | ----------- |
333
+
|`apiKey`| string | Yes | Luma API key |
334
+
|`eventId`| string | Yes | Event ID \(starts with evt-\)|
335
+
|`guests`| string | Yes | JSON array of guest objects. Each guest requires an "email" field and optionally "name", "first_name", "last_name". Example: \[\{"email": "user@example.com", "name": "John Doe"\}\]|
336
+
337
+
#### Output
338
+
339
+
| Parameter | Type | Description |
340
+
| --------- | ---- | ----------- |
341
+
|`added`| number | Number of guests submitted to the event \(added with Going/approved status\)|
342
+
343
+
### `luma_send_invites`
344
+
345
+
Send email invitations to guests for a Luma event. Unlike Add Guests (which registers guests directly), this emails an invite that recipients can accept.
346
+
347
+
#### Input
348
+
349
+
| Parameter | Type | Required | Description |
350
+
| --------- | ---- | -------- | ----------- |
351
+
|`apiKey`| string | Yes | Luma API key |
352
+
|`eventId`| string | Yes | Event ID to invite guests to \(starts with evt-\)|
353
+
|`guests`| string | Yes | JSON array of guest objects. Each guest requires an "email" field and optionally "name". Example: \[\{"email": "user@example.com", "name": "John Doe"\}\]|
354
+
|`message`| string | No | Optional custom message included in the invite email \(max 200 characters\)|
355
+
356
+
#### Output
357
+
358
+
| Parameter | Type | Description |
359
+
| --------- | ---- | ----------- |
360
+
|`invited`| number | Number of guests invited to the event |
361
+
362
+
### `luma_update_guest_status`
363
+
364
+
Update a guest
365
+
366
+
#### Input
367
+
368
+
| Parameter | Type | Required | Description |
369
+
| --------- | ---- | -------- | ----------- |
370
+
|`apiKey`| string | Yes | Luma API key |
371
+
|`eventId`| string | No | Event ID the guest belongs to \(starts with evt-\)|
372
+
|`guestIdentifier`| string | Yes | Guest email address or guest ID \(gst-...\). Values containing '@' are treated as emails; otherwise as a guest ID. |
373
+
|`status`| string | Yes | New approval status: approved, declined, pending_approval, or waitlist |
374
+
|`shouldRefund`| boolean | No | Refund a paid guest when moving them out of an approved state \(defaults to false\)|
375
+
|`sendEmail`| boolean | No | Whether to email the guest about the status change \(defaults to true\)|
376
+
377
+
#### Output
378
+
379
+
| Parameter | Type | Description |
380
+
| --------- | ---- | ----------- |
381
+
|`status`| string | The approval status applied to the guest |
382
+
|`guest`| string | The guest identifier \(email or ID\) that was updated |
0 commit comments