Meetings
| Tool | What it does |
|---|---|
booking_links_list | List the caller’s own meeting booking links (My meeting links) and their booking-page settings. |
meeting_add_notes | Append a stamped note to one accessible meeting. |
meeting_availability | Check a teammate’s open booking slots for one of their meeting links over a date range, to find a time to book a meeting on their behalf. |
meeting_cancel | Cancel an owned meeting and its calendar event after approval. |
meeting_get | Get full details for one meeting: schedule, status, host, guests, notes, activity trail, and recording, by meeting id. |
meeting_host_list | List teammates who can host a meeting and whether each one is bookable right now, for scheduling a meeting on someone’s behalf. |
meeting_reschedule | Move an owned meeting to the approved time. |
meeting_schedule | Book a meeting on an eligible teammate’s calendar after approval. |
meeting_search | Search or filter the caller’s own meetings by title, guest name or email, company, date range, status (upcoming, no-show, canceled), booking source, meeting link, whether it was recorded, or a phrase said in the recording. |
booking_links_list
List the caller’s own meeting booking links (My meeting links) and their booking-page settings.
List the caller’s own meeting-link ‘types’ (the My meeting links tab), optional name search, plus the personal booking-hub summary (slug, public URL, default link, calendar connection state). Use to resolve a link’s id/name/duration before meeting_schedule, or when the user asks what booking links they have.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/booking-links-list |
| MCP tool | booking_links_list on https://mcp.prospeo.io |
| Effect | Reads data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Not needed. |
| Pagination | Returns one page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
| Parameter | Type | Required | Description |
|---|---|---|---|
search | string | No | Optional name substring to filter the caller’s own meeting links, up to 200 characters. Length 0 to 200. |
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.
meeting_add_notes
Append a stamped note to one accessible meeting.
Append a timestamped, team-visible note to a meeting — an atomic $push, never an overwrite — with optional @-mentions of teammates who can already see the meeting. Never sent to the guest. Use to record call notes or context the user wants preserved on the meeting.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/meeting-add-notes |
| MCP tool | meeting_add_notes on https://mcp.prospeo.io |
| Effect | Changes data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Not needed. |
| Pagination | Returns one page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
| Parameter | Type | Required | Description |
|---|---|---|---|
meeting_id | string | Yes | MongoDB ObjectId Pattern ^[0-9a-fA-F]{24}$. |
text | string | Yes | Length 1 to 2000. |
mentions | array of string | No | Up to 50 items. |
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.
meeting_availability
Check a teammate’s open booking slots for one of their meeting links over a date range, to find a time to book a meeting on their behalf.
Compute a picked teammate’s bookable time slots for one of their ACTIVE meeting links, honoring the link’s duration/interval/buffers/date range but with the minimum-notice floor WAIVED (the rep-assisted widget can book to the last minute). Use right before meeting_schedule to show the user real open slots for a host+link pair.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/meeting-availability |
| MCP tool | meeting_availability on https://mcp.prospeo.io |
| Effect | Reads data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Not needed. |
| Pagination | Returns one page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
| Parameter | Type | Required | Description |
|---|---|---|---|
host_oid | string | Yes | The teammate to check availability for, from meeting_host_list. Pattern ^[0-9a-fA-F]{24}$. |
link_id | string | Yes | The host’s own ACTIVE meeting-link oid to check availability against, from booking_links_list. Pattern ^[0-9a-fA-F]{24}$. |
start_date | string | Yes | Start of the date range to check, inclusive (ISO 8601 date, e.g. 2026-09-10). |
end_date | string | Yes | End of the date range to check, inclusive (ISO 8601 date); server-clamped to the link’s own booking-range-days limit. |
timezone | string | No | IANA timezone name the returned slots are expressed in, up to 64 characters. Omit it to use the user’s own booking timezone. Length 0 to 64. Default "UTC". |
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.
meeting_cancel
Cancel an owned meeting and its calendar event after approval.
Host-cancel a scheduled meeting: deletes the calendar event, notifies the guest, cancels the reminder, and tears down any scheduled recorder. Only meetings booked via the booking page or the schedule-meeting widget can be canceled here (not RECORDER_INVITE/AD_HOC/Gong-import rows). Idempotent if already canceled. Always confirm before calling — this notifies a real external attendee and cannot be reversed.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/meeting-cancel |
| MCP tool | meeting_cancel on https://mcp.prospeo.io |
| Effect | Deletes or removes data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Recommended: MCP clients should confirm with the user before calling. |
| Pagination | Returns one page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
| Parameter | Type | Required | Description |
|---|---|---|---|
meeting_id | string | Yes | MongoDB ObjectId Pattern ^[0-9a-fA-F]{24}$. |
reason | string | No | Length 0 to 2000. |
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.
meeting_get
Get full details for one meeting: schedule, status, host, guests, notes, activity trail, and recording, by meeting id.
Load one meeting’s full detail for the single-meeting view: schedule window, guests, host, derived status (including whether/how many times it was rescheduled) + its hover context, notes, activity trail, reschedule history, booker, and the recording chip. Use once meeting_list/meeting_search has resolved a meeting_id and the user wants the full record.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/meeting-get |
| MCP tool | meeting_get on https://mcp.prospeo.io |
| Effect | Reads data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Not needed. |
| Pagination | Returns one page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
| Parameter | Type | Required | Description |
|---|---|---|---|
meeting_id | string | Yes | The meeting’s oid, from a prior meeting_search result. Pattern ^[0-9a-fA-F]{24}$. |
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.
meeting_host_list
List teammates who can host a meeting and whether each one is bookable right now, for scheduling a meeting on someone’s behalf.
List every teammate for the [Schedule meeting] widget’s host picker, each flagged whether they’re currently bookable (healthy connected calendar AND at least one ACTIVE meeting link) with a disabled_reason when not, sorted self-first then alphabetically. Use as the first step of meeting_schedule to resolve a host_oid.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/meeting-host-list |
| MCP tool | meeting_host_list on https://mcp.prospeo.io |
| Effect | Reads data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Not needed. |
| Pagination | Returns one page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
This endpoint takes an empty body: {}.
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.
meeting_reschedule
Move an owned meeting to the approved time.
Host-reschedule a scheduled meeting to a new [start, end) in place — same row, same manage link, same conferencing link — patching the real calendar event and notifying the guest. Only the future-start rule binds host-side (no minimum-notice/grid-legality check). The former window is kept in reschedule_history, so this is fully reversible by rescheduling again. Always confirm the new time with the user first — it notifies a real external attendee.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/meeting-reschedule |
| MCP tool | meeting_reschedule on https://mcp.prospeo.io |
| Effect | Changes data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Recommended: MCP clients should confirm with the user before calling. |
| Pagination | Returns one page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
| Parameter | Type | Required | Description |
|---|---|---|---|
meeting_id | string | Yes | MongoDB ObjectId Pattern ^[0-9a-fA-F]{24}$. |
start | string | Yes | |
end | string | Yes | |
reason | string | No | Length 0 to 2000. |
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.
meeting_schedule
Book a meeting on an eligible teammate’s calendar after approval.
Book a meeting on a picked teammate’s calendar (the rep-assisted widget): a guest name+email, optional additional guest emails, and a [start, end) window on one of the host’s own ACTIVE meeting links. Runs the same BookingEngine the public booking page uses (source=REP_BOOKED, minimum-notice/grid-legality skipped; overlap, provider freebusy and the link’s booking cap still enforced) and sends a real calendar invite to the guest.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/meeting-schedule |
| MCP tool | meeting_schedule on https://mcp.prospeo.io |
| Effect | Changes data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Recommended: MCP clients should confirm with the user before calling. |
| Pagination | Returns one page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
| Parameter | Type | Required | Description |
|---|---|---|---|
host_oid | string | Yes | MongoDB ObjectId Pattern ^[0-9a-fA-F]{24}$. |
link_id | string | Yes | MongoDB ObjectId Pattern ^[0-9a-fA-F]{24}$. |
guest_name | string | Yes | Length 1 to 155. |
guest_email | string | Yes | Length 1 to 255. |
guest_emails | array of string | No | |
start | string | Yes | |
end | string | Yes | |
timezone | string | Yes | Length 1 to 64. |
note | string | No | Length 0 to 2000. |
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.
meeting_search
Search or filter the caller’s own meetings by title, guest name or email, company, date range, status (upcoming, no-show, canceled), booking source, meeting link, whether it was recorded, or a phrase said in the recording.
Search and filter the caller’s own personal meetings: free text over meeting title, guest name/email, and company name; upcoming/past/custom date window; display-status tags (including no-show and both cancel tags); booking source; meeting-link/type; whether a completed recording exists; primary guest email; and conversation-keyword phrase groups matched against the linked recording’s transcript. Use whenever the user names any criterion; use meeting_list for a bare browse.
| Endpoint | POST https://api.prospeo.io/api/v2/tools/meeting-search |
| MCP tool | meeting_search on https://mcp.prospeo.io |
| Effect | Reads data. |
| Credits | Free, uses no credits. |
| Permission | No role permission beyond API access. |
| Confirmation | Not needed. |
| Pagination | Page-based: page. |
Request
Send POST with your API key in the X-KEY header and a JSON body. Unknown fields and query parameters are rejected. The full JSON Schema is served with the tool list.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | No | Page number, starting at 1, 25 meetings per page. From 1 to 100000. Default 1. |
search | string | No | Free text over meeting title, guest name/email, and company name, up to 200 characters. Length 0 to 200. |
date | string (enum) | No | Date posture: AFTER_TODAY (upcoming, default), BEFORE_TODAY, CUSTOM (reads custom_start/custom_end), NOT_ENDED, ENDED, or ALL (no date filter). One of: AFTER_TODAY, BEFORE_TODAY, CUSTOM, NOT_ENDED, ENDED, ALL. Default "AFTER_TODAY". |
custom_start | string | No | Start of the date window (ISO 8601); only read when date is CUSTOM. |
custom_end | string | No | End of the date window (ISO 8601); only read when date is CUSTOM. |
status | array of string (enum) | No | Display-status tags to include (any of the 7 values); empty means no status filter. Up to 7 items. Items one of: CANCELED_BY_GUEST, CANCELED_BY_HOST, NO_SHOW, IN_PROGRESS, TODAY, UPCOMING, COMPLETED. |
source | array of string (enum) | No | Booking-source values to include; empty means no source filter. Up to 5 items. Items one of: BOOKING_PAGE, FORM, REP_BOOKED, RECORDER_INVITE, AD_HOC, GONG_IMPORT. |
link_oids | array of string | No | Meeting-link oids to include (the ‘Meeting type’ facet), up to 50. Up to 50 items. |
include_no_link | boolean | No | Also include meetings booked with no meeting-link; ORs with link_oids rather than narrowing it. Default false. |
was_recorded | boolean | No | True for meetings with a finished recording, False for meetings without one, omitted for both. |
primary_guest_email | string | No | Match the primary guest’s exact email address, up to 320 characters. Length 0 to 320. |
keywords_include_any | array of string | No | Match a meeting whose recording transcript contains ANY of these phrases (each up to 100 characters), up to 25 phrases. Up to 25 items. |
keywords_include_all | array of string | No | Match a meeting whose recording transcript contains ALL of these phrases (each up to 100 characters), up to 25 phrases. Up to 25 items. |
keywords_exclude | array of string | No | Exclude meetings whose recording transcript contains any of these phrases (each up to 100 characters), up to 25 phrases. Up to 25 items. |
sort | string (enum) | No | Sort field: START (schedule start time, default) or TITLE (alphabetical). One of: START, TITLE. Default "START". |
sort_direction | string (enum) | No | Sort direction ASC or DESC; omitted keeps the date posture’s own historical default direction. One of: ASC, DESC. |
include_facets | boolean | No | Whether to also compute and return facet counts for this search; adds cost, so defaults to false for a tool call. Default false. |
Response
{"ok": true, "summary": "...", "payload": {...}} on success. Errors return {"ok": false, "code", "message", "retryable"}; see error codes.