Skip to main content
Glama

List Guests

list_guests
Read-onlyIdempotent

List guests at an event you manage, including the latest signups/newest additions. Free RSVPs, guest-list adds, comps and paid tickets — with name, email, phone, category, plus-ones, source (rsvp/guest_list/paid/comp) and check-in status, plus totals per source and the checked-in count. Cancelled/refunded tickets left out; staff only with include_staff. Optional category/source filters; limit selects latest N ticket records (1-500). Newest first by createdAt (ISO UTC), unknown dates last. newestOrderComplete and coverageNote disclose missing dates/incomplete scans; totalIsExact covers summary counts. Multiple tickets can belong to one person. Requires event_id; you must be a host. Read-only.

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": {
      "event_id": "<event_id>"
    },
    "name": "list_guests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
sourceNo
categoryNo
event_idYes
page_sizeNo
include_staffNo
updated_sinceNo
include_registration_answersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "maxLength": 4096,
      +  "type": "string"
      +}
    • addedInput schema / properties / event_id / pattern
      Added value: +"^[^/]+$"
    • addedInput schema / properties / include_registration_answers
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / page_size
      Added value: +{
      +  "maximum": 200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / updated_since
      Added value: +{
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / include_staff
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "enum": [
      +    "rsvp",
      +    "guest_list",
      +    "paid",
      +    "comp",
      +    "staff",
      +    "host",
      +    "other"
      +  ],
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial behavior beyond them: newest-first ordering by createdAt with unknown dates last, exclusion of cancelled/refunded tickets, host authorization, multiple tickets per person, and the newestOrderComplete/coverageNote/totalIsExact flags that signal incomplete date coverage.

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?

Dense but front-loaded: the core purpose and payload come first, then filters, ordering, and caveats. The semicolon-chained sentences pack a lot of facts efficiently, though the run-on structure makes the pagination behavior easy to miss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter list tool with no output schema and zero schema descriptions, the description does well on return values (fields, per-source totals, checked-in count) and edge cases. The significant gap is that two overlapping pagination mechanisms (limit vs. cursor/page_size) and updated_since are left unaddressed, which is exactly the ambiguity an agent would hit when paging through a large guest list.

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 description coverage is 0%, so the description must carry the load, and it explains only some parameters: event_id, category/source filters, limit (1-500), and include_staff. The pagination and incremental parameters — cursor, page_size, and updated_since — plus include_registration_answers are never mentioned, leaving roughly half the inputs unexplained in both places.

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?

States a specific verb and resource ('List guests at an event you manage') and immediately scopes what is included: RSVPs, guest-list adds, comps, paid tickets, and the exact fields returned. An agent can distinguish this from export_guest_list_csv or list_my_tickets without opening either schema, because the description enumerates fields, sources, and check-in status.

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?

Gives usable context: requires event_id, you must be a host, cancelled/refunded are excluded, and staff appear only with include_staff. It never names an alternative tool or states when a caller should prefer export_guest_list_csv or list_my_tickets instead, so the guidance is clear but not routing.

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.