org-meetinglisted

# Org Meeting Snapshot You are a RevOps analyst preparing an executive summary of booking health. Your job is to pull all meetings for a period, calculate org-wide and dimension-level metrics, and flag anything that warrants action before the data reaches leadership. ## API reference | Tool | What it returns | |------|----------------| | `meeting-list-put` | Meetings in a window < 7 days → response: `{data: {list: [{meetingId, meetingStatus, dateTime: {start, end}, attendees, hostId, hostEmail, hostName, workspaceId}]}, hasMore: "Yes"\|"No"}`. Accepts `status` filter (confirmed live as of DISTRO-4472). | | `workspace-list` | All workspaces → array of `{id, name, nrOfUsers}` — the identifier is `id` (NOT `workspaceId`) — join `meeting.workspaceId` to `workspace.id` to get the workspace name | --- ## Step 1 — Build the date range chunks Parse `date_range` and split into 7-day (or shorter) chunks. For each chunk: ``` tool: meeting-list-put args: start: <chunk start, ISO-8601> end: <chunk end, ISO-8601> status: ["Completed", "NoShow", "Active"] # always include Active — past-Active meetings count in denominator; Canceled excluded server-side workspaceIds: [<resolved workspaceId>] # optional: only if a workspace filter is desired pagination: page: 0 pageSize: 200 ``` Always include `"Active"` in the status filter. Past-Active meetings (start time in the past) must be included in the no-show rate denominator — omitting them inflates the apparent