Skip to main content
Glama

Create an event invite link

status_create_event

Create a shareable event invite link where guests RSVP, for a party, dinner, birthday, trip, night out or other get-together; the host can then add a date poll and split costs on the same page. Use when the user is planning something with other people and wants a link to send round. Not for calendar entries, solo reminders, one-to-one meetings or selling tickets to public events. Only title is required; details, location, date, time, timeZone, theme and hostName are optional. No account or API key. Returns claimUrl (private to the user: opening it and signing in makes them the host; until then the event is a draft and guests cannot join), inviteUrl (for guests, works once claimed), eventUrl, eventId and editKey (for status_get_event and status_update_event, valid 7 days).

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": {
      "title": "<title>"
    },
    "name": "status_create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoEvent date as YYYY-MM-DD. Leave out if the date is not set yet
timeNoStart time as 24-hour HH:mm, local to timeZone, e.g. 19:30. Needs date
themeNoVisual style of the invite page: party, dinner, garden, sport, holiday, plain. Defaults to party
titleYesEvent name shown at the top of the invite, e.g. "Sam's 30th" or "Book club dinner"
detailsNoInvite message for guests: what is happening, what to bring, dress code, cost per person
hostNameNoThe user's first name, shown as host on the invite until they claim it
locationNoVenue name or address, e.g. "The Albion, Bristol"
timeZoneNoIANA time zone for date and time, e.g. Europe/London (the default) or America/New_York

Output Schema

NameRequiredDescriptionDefault
eventNoThe event as guests see it
editKeyYesCredential for status_update_event and status_get_event. Valid for 7 days.
eventIdYes
messageYesPlain-language summary of the result
claimUrlYesPrivate link for the user only: opening it and signing in makes them the host
inviteUrlYesInvite link for guests; works once the user has claimed the event

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent and closed-world, so the safety profile is covered; the description nonetheless adds substantial context the annotations cannot express — no account or API key required, the claimUrl/claim-to-become-host flow, the draft state in which guests cannot join, inviteUrl only working after claiming, and a 7-day editKey lifetime. The one notable omission is that non-idempotency is never spelled out behaviorally (i.e. calling twice presumably yields two distinct events). Strong added value overall, held below the top mark only by that gap.

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?

Purpose, exclusions, parameter requirements and return values appear in that deliberate order, front-loading what an agent needs to make the selection decision. It is dense and the final return-values sentence is a long semicolon chain, but no sentence is filler.

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 an 8-parameter creation tool with an output schema, the description covers everything consequential: required vs optional inputs, the no-auth precondition, the draft/claim lifecycle, and the meaning and expiry of each returned URL and key. The claimUrl semantics especially would be unguessable from the output schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter carries a description with format guidance (YYYY-MM-DD, 24-hour HH:mm, IANA time zone, theme enum, max lengths), so the schema does the heavy lifting. The description only restates that title is required and the rest optional, adding no format or interaction semantics beyond that — baseline 3 is appropriate.

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 — "Create a shareable event invite link where guests RSVP" — and enumerates concrete use cases (party, dinner, birthday, trip, night out) plus the follow-on capabilities (date poll, cost splitting). It also explicitly carves itself away from calendar entries, solo reminders, one-to-one meetings and ticket sales, so an agent can distinguish it from adjacent tools 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 Guidelines5/5

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

"Use when the user is planning something with other people and wants a link to send round" gives a positive trigger condition, and the following sentence gives four explicit exclusions. It also names status_get_event and status_update_event as the consumers of editKey, implicitly routing follow-up calls.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources