Skip to main content
84 tools. 82 are backed one-to-one by the Bolna REST API and act on your account. The remaining 2 (search_docs, get_doc) read Bolna’s public documentation instead — no account data involved. The 23 tools are update_agent, delete_agent, start_outbound_call, schedule_batch, delete_batch, delete_disposition, buy_phone_number, delete_phone_number, delete_sip_trunk, delete_sub_account, remove_provider, delete_knowledgebase, rename_workflow, delete_workflow, save_workflow_draft, publish_workflow, run_workflow, delete_workflow_campaign, start_workflow_campaign, pause_workflow_campaign, resume_workflow_campaign, abort_workflow_campaign, and cancel_workflow_execution — see each one’s row below for what makes it destructive.

Calling tools with a different account

Every tool below also accepts an optional api_key argument. Pass it on any single call to run that call against a different account than the one your client connected with — without reconnecting. This is for sub-accounts: call list_sub_accounts to get a sub-account’s key (sa-...), then pass it as api_key on any later tool call to act as that sub-account for just that call. A sub-account key also works as the primary connection credential from the start, exactly like a main account’s bn-... key — see the Quickstart.

Agents

Calls & executions

Batches

Dispositions

Dispositions turn a call transcript into structured, typed data — lead qualified, appointment time, sentiment — surfaced as extracted_data on executions and webhook payloads.

Knowledgebase (RAG)

create_knowledgebase only accepts a URL to scrape — the Bolna API also supports uploading a PDF directly, but a raw file doesn’t map cleanly to a chat tool argument. For PDF-based knowledgebases, use the dashboard or call the Create Knowledgebase API directly.

Phone numbers & inbound

SIP trunks

For bringing your own telephony (BYOT) — Twilio Elastic SIP, Plivo Zentrunk, Telnyx, and other standards-compliant trunks.

Sub-accounts

Enterprise feature — isolated workspaces with their own auto-provisioned API key (sa-...), agents, calls, and phone numbers, for agencies, multi-tenant platforms, or regulated data boundaries.

Voice & providers

Violations

Workflows

Multi-step, per-contact automations — call an agent, branch on the outcome, wait, call an API, message over WhatsApp, retry, and so on — distinct from a single agent’s own conversation. A workflow is edited as a draft, then published as an immutable version before it can run.

Workflow campaigns

Runs many contacts through one pinned, published workflow version — the workflow equivalent of a batch running many contacts through one agent.

Workflow executions

A single contact’s run through a workflow, created by run_workflow or a campaign.

Account

Documentation

These two don’t touch your account at all — they read Bolna’s own docs, so the assistant can look things up instead of guessing. Not connected yet? See the Quickstart for setup and troubleshooting.

Bolna MCP Server Repository

Full source, endpoint-verification notes, and issue tracker