> ## Documentation Index > Fetch the complete documentation index at: https://docs.zuddl.com/llms.txt > Use this file to discover all available pages before exploring further. # List Attendees > **Tool name:** `v1_list_attendees` ยท **Behaviour:** ๐Ÿ”’ Read-only List all attendees registered for a particular event in your Zuddl organization, paginated. Filterable via the filters parameter (see its schema): firstName, lastName, company, designation, industry, country, createdAt, updatedAt. Always ordered by registration time (newest first); custom sorting is not available through this tool. pagination.next in the response is non-null when another page exists โ€” call again with the same filters and the next page number until it is null. **Same as Public API:** [Get all attendee details](/api-reference/attendees/get-all-attendee-details) (`GET /v1/events/{eventId}/attendees`) ## OpenAPI ````yaml https://api.prod.zuddl.com/api/v3/api-docs/mcp-tools post /tools/v1_list_attendees openapi: 3.1.0 info: title: Zuddl MCP Tools Reference description: >- The Zuddl MCP server lets AI assistants such as Claude and ChatGPT work with your Zuddl organization through the [Model Context Protocol](https://modelcontextprotocol.io). This reference lists every tool the server offers. It is generated from the live server, so it always matches what your assistant sees. # Connecting Add `https://setup.zuddl.com/api/mcp` as a remote MCP server in your assistant. It signs you in to Zuddl with OAuth and then calls tools on your behalf, with your permissions. AI features must be enabled for your organization. # Calling a tool Assistants call a tool with a JSON-RPC `tools/call` request whose `name` is the tool name and whose `arguments` match the request body documented on the tool's page. The `/tools/` paths in this reference identify tools; they are not HTTP endpoints. # Behaviour labels | Label | Meaning | | --- | --- | | ๐Ÿ”’ Read-only | Reads data and changes nothing. | | โœ๏ธ Write | Creates or updates data, but does not delete it. | | โš ๏ธ Destructive | Deletes or removes data. Most assistants ask you to approve these calls. | | ๐Ÿ” Idempotent | Calling it again with the same arguments has no further effect. | A tool that mirrors a Public API endpoint links to that endpoint's page. MCP-only tools have no Public API equivalent. version: 1.0.0 servers: - url: https://setup.zuddl.com/api/mcp description: Zuddl MCP server security: - oauth: [] tags: - name: Events - name: Attendees - name: Sessions - name: Speakers - name: Sponsors - name: Locations - name: Teams - name: Brand Kits - name: Registration flows & tickets - name: Analytics paths: /tools/v1_list_attendees: post: tags: - Attendees summary: List Attendees description: >- **Tool name:** `v1_list_attendees` ยท **Behaviour:** ๐Ÿ”’ Read-only List all attendees registered for a particular event in your Zuddl organization, paginated. Filterable via the filters parameter (see its schema): firstName, lastName, company, designation, industry, country, createdAt, updatedAt. Always ordered by registration time (newest first); custom sorting is not available through this tool. pagination.next in the response is non-null when another page exists โ€” call again with the same filters and the next page number until it is null. **Same as Public API:** [Get all attendee details](/api-reference/attendees/get-all-attendee-details) (`GET /v1/events/{eventId}/attendees`) operationId: v1_list_attendees requestBody: description: The tool's `arguments`, as sent in a JSON-RPC `tools/call` request. content: application/json: schema: type: object additionalProperties: false properties: eventId: type: string description: Unique identifier of the event. filters: type: array description: > Filter criteria. ALL criteria are combined with AND; for an OR across different fields, call this tool once per condition. To match any of several values of the SAME field, use one criterion with the in operation (e.g. status in [PENDING, APPROVED]). Each criterion applies one operation to one field. Only the field/operation combinations listed below are valid: - profile.firstName (operations: like, not_like): Attendee first name. Combine with lastName for a precise full-name search. - profile.lastName (operations: like, not_like): Attendee last name. Combine with firstName for a precise full-name search. - profile.company (operations: like, not_like): Attendee company name (substring match via like). - profile.designation (operations: like, not_like): Attendee job title / designation (e.g. 'CTO', 'Product Manager'). - profile.industry (operations: eq, in, like): Industry of the attendee's company (e.g. 'Information Technology'). - profile.country (operations: eq, in): Country the attendee provided at registration. - createdAt (operations: eq, between, gt, gte, lt, lte): When the registration was created. ISO-8601 with offset, e.g. 2026-05-01T00:00:00Z. Use gte/lte for open ranges or between for a closed range. Values: ISO-8601 date-time with offset, e.g. 2026-05-01T00:00:00Z. - updatedAt (operations: eq, between, gt, gte, lt, lte): When the registration was last updated. ISO-8601 with offset, e.g. 2026-05-01T00:00:00Z. Use gte/lte for open ranges or between for a closed range. Values: ISO-8601 date-time with offset, e.g. 2026-05-01T00:00:00Z. items: type: object additionalProperties: false properties: field: type: string enum: - profile.firstName - profile.lastName - profile.company - profile.designation - profile.industry - profile.country - createdAt - updatedAt operation: type: string description: >- eq = equals, in = any of the values, like = case-sensitive substring match, ilike = case-insensitive substring match, not_like = negated like, not_ilike = negated ilike, gt / gte / lt / lte = comparison, between = inclusive range. enum: - like - not_like - eq - in - between - gt - gte - lt - lte values: type: array description: >- Exactly 1 value for every operation except: in (1 or more) and between (exactly 2). items: type: string minItems: 1 required: - field - operation - values page: type: integer description: 1-based page number. Defaults to 1. size: type: integer description: Number of results per page. Defaults to 10, maximum 100. required: - eventId required: true responses: '200': description: A JSON-RPC `tools/call` result. The tool's output is in `content`. components: securitySchemes: oauth: type: http description: >- OAuth 2.1 access token. MCP clients obtain it themselves (dynamic client registration + PKCE) when you connect them to the server URL above. scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.