> ## Documentation Index > Fetch the complete documentation index at: https://docs.ringee.io/llms.txt > Use this file to discover all available pages before exploring further. # Tool reference > Every tool the Ringee MCP server exposes The Ringee MCP server exposes 19 tools. Each is annotated with MCP trust hints so clients can decide when to ask for confirmation. Trust levels are colour-coded throughout this tab:

Read looks, never changes anything · Write creates or updates a record · Sensitive spends money or mints a shareable link · Destructive removes access or data

| Tool | Type | Spends credits | | ------------------------------------------------------- | ------------------------------------------------------------ | -------------- | | [`list_workspaces`](#list_workspaces) | Read | No | | [`switch_workspace`](#switch_workspace) | Write | No | | [`search_contacts`](#search_contacts) | Read | No | | [`get_contact`](#get_contact) | Read | No | | [`find_contacts_by_outcome`](#find_contacts_by_outcome) | Read | No | | [`list_calls`](#list_calls) | Read | No | | [`create_contact`](#create_contact) | Write | No | | [`update_contact`](#update_contact) | Write | No | | [`delete_contact`](#delete_contact) | Destructive | No | | [`log_call_outcome`](#log_call_outcome) | Write | No | | [`create_callback`](#create_callback) | Write | No | | [`schedule_meeting`](#schedule_meeting) | Write | No | | [`create_call_session`](#create_call_session) | Sensitive | No | | [`get_call_session`](#get_call_session) | Read | No | | [`update_call_session`](#update_call_session) | Write | No | | [`delete_call_session`](#delete_call_session) | Destructive | No | | [`search_leads`](#search_leads) | Read | Provider only | | [`reveal_lead`](#reveal_lead) | Sensitive | Provider only | | [`import_leads_as_contacts`](#import_leads_as_contacts) | Write | No | No MCP tool ever debits Ringee calling credits. `search_leads` and `reveal_lead` consume the allowance of your connected enrichment provider (Apollo or Prospeo). ## Conventions * Phone numbers are **E.164**: `+14155552671`. * Dates and times are **ISO-8601 with a timezone offset**: `2026-05-23T14:30:00-04:00`. * Ids are UUIDs returned by other tools. Never invent one. * Paginated tools accept `page` (1-based, default `1`) and `limit` (default `10`, max `50`). *** ## Workspaces ### `list_workspaces` Lists the personal account plus every organization the user belongs to, and flags the active one. Takes no parameters. ### `switch_workspace` Changes the active workspace for every subsequent action. No re-authentication needed. `personal` for the user's own account, or an organization id from `list_workspaces`. An exact organization name also works. See [Workspaces](/mcp/workspaces) for how scoping behaves. *** ## Contacts ### `search_contacts` Searches the directory by name, phone, email, company, job title, state, website, revenue or company size. Returns id, name, phone, email and `lastCallAt`. Search text. Pass `*` to list **all** contacts, paginated. 1-based page number. Page size, max 50. Use this to resolve a `contactId` before any tool that needs one. ### `get_contact` Fetches one contact in full, including recent calls, notes, meetings and tags. The contact to fetch. ### `find_contacts_by_outcome` Finds contacts whose calls reached given outcomes — who converted, showed interest or booked a meeting. Useful for deriving a real ICP from closed business. One or more of `meeting_booked`, `sale`, `interested`, `follow_up`, `callback_scheduled`, `not_interested`, `no_answer`, `voicemail`, `wrong_number`, `gatekeeper`. `any` (default) matches a contact with **any** call in those outcomes. `last` considers only the most recent call. Include contacts flagged `doNotCall` or `unsubscribed`. Defaults to `false`. 1-based page number. Page size, max 50. Returns ICP-relevant fields — company, job title, seniority, department, country, score, lifecycle stage — plus `lastOutcome` and `lastCallAt`. ### `create_contact` E.164. Must be unique within the workspace — the tool fails fast on a duplicate. Display name. Given name. Family name. Primary email. Role at the company. Company name. State or region. Company website. Company revenue or range. Headcount band. Lead source label. Defaults to `mcp`. Initial note. Tag UUIDs to assign. ### `update_contact` Patches an existing contact. Only the fields you send change. The contact to update. **Replaces** the contact's tag set. Omit it to leave tags untouched. All other fields match `create_contact`. Ownership is verified before writing. ### `delete_contact` Destructive Soft-deletes a contact by setting `deletedAt`. The contact to delete. Must be the literal `true`. Must exactly match the contact's stored phone number in E.164. Destructive and double-guarded. Fetch the contact with `get_contact` first, read the phone number back to the user, and get an explicit "yes, delete" before calling. Assistants must never auto-confirm. *** ## Calls and follow-ups ### `list_calls` Returns calls in full detail: direction, status, timing, duration, logged outcome and note, plus the transcription and recording URL when present. Newest first. Cost and low-level telephony fields are intentionally excluded. Filter to one contact's calls. Only calls with one of these outcomes. Only calls in these states: `pending`, `ringing`, `answered`, `recording`, `completed`, `failed`. Only calls created at or after this. Only calls created at or before this. 1-based page number. Page size, max 50. ### `log_call_outcome` Records how a past call went. An existing call belonging to the active workspace. One of the `CallOutcome` values listed under `find_contacts_by_outcome`. Free-text note. ### `create_callback` Schedules a reminder to call a contact back. Creates a callback task and a reminder. Who to call back. Future datetime with offset. Originating call. Free-text note. ### `schedule_meeting` Books a meeting. When the user has a Google or Microsoft calendar connected, the event is synced and a Meet or Teams link is generated. Who the meeting is with. Start time with offset. Meeting title. Minutes. Defaults to 30. Address or video URL. Notes. Sends a calendar invite to this address. Calendar to sync with. Originating call. This tool reaches an external system (calendar sync and email invites), so it is flagged `openWorldHint`. *** ## Call sessions A **call session** is a queue of contacts plus a magic link that lets someone dial through them one by one — without logging in. ### `create_call_session` Sensitive Ordered queue, 1 to 500 entries. Each accepts `contactId` and/or `phoneNumber` (E.164, required when `contactId` is absent), plus optional `name`, `company`, `jobTitle`, `state`, `website`, `revenue`, `companySize`. Provide `contactId` when you have it — name and phone are then looked up server-side. Session title, visible to the magic-link recipient. Attribute calls to a campaign. Link lifetime. Defaults to 60 minutes, max 30 days. Auto-complete the session after N calls, max 500. Free-form JSON persisted with the session; not exposed to the magic-link UI. Returns a `joinUrl` containing a magic-link token. The token is shown **once** and cannot be re-fetched. Share the URL exactly as returned, and only with someone authorized to call on the workspace's behalf. ### `get_call_session` Returns safe metadata — status, contact count, calls completed, expiry, and whether a token is still active. It never exposes the raw magic link. The session to inspect. ### `update_call_session` The session to update. New title. Set a campaign, or `null` to detach. Extend validity. Replaces the queue. Only allowed **before the first call** has started. Replace metadata. ### `delete_call_session` Destructive Revokes the session. Past calls are preserved, but every active magic link stops working immediately. The session to revoke. Flagged destructive — the link cannot be restored. Issue a new session instead. *** ## Lead prospecting These tools use the workspace's connected enrichment provider. Apollo is preferred when both are connected. ### `search_leads` Searches for candidates. Results are **not** contacts yet. `apollo` or `prospeo`. Auto-selected when omitted. Free-text keywords. Job titles to include. Job titles to exclude. Seniority levels. Departments. Countries. Cities. Industries. Company names. Company domains. Headcount bands. Technologies in use. Only candidates with an email. Only candidates with a phone. Only verified emails. Page number. Results per page, max 25. Returns a `jobId` plus candidates with `externalId`, person and company summaries, and whether emails and phones are available. Pass the `jobId` to the two tools below. ### `reveal_lead` Sensitive Spends provider credits Reveals a candidate's email — and optionally a mobile phone — and upserts a Ringee contact so the lead is immediately callable. From `search_leads`. The candidate to reveal. Also reveal a mobile phone. Costs extra provider credits. Spends the enrichment provider's credits every time and is **not** idempotent. Call it only after the user explicitly picks that lead. ### `import_leads_as_contacts` Bulk-imports candidates from a search job as Ringee contacts, deduplicated by phone number. Does **not** reveal hidden emails or phones — use `reveal_lead` first if you need those. From `search_leads`. Candidates to import. Tags to assign to every imported contact. Returns counts, duplicates, errors and the new contact ids. *** ## Placing calls There is no tool that dials a number. Calls are placed in the user's browser or mobile app over WebRTC, so an assistant cannot start one server-side. To get someone dialing from a chat, use `create_call_session` and share the `joinUrl`. ## Next steps How personal and organization scoping works Confirmation rules for sensitive actions