Skip to main content
Paste any of these into a connected client. Each one links to the tool it triggers — see the Tool List for the full schema.

Agents

Triggers list_agents.
Triggers get_agent.
Triggers create_agent.
Triggers update_agent — most clients ask you to confirm first.
Triggers stop_agent_queued_calls.
Triggers delete_agent — irreversible, most clients ask you to confirm first.

Graph agents

Uses the design_graph_agent prompt for the design, then triggers create_graph_agent, which validates the graph before saving.
Triggers get_graph_agent.
Triggers get_graph_agent, then update_graph_agent. Most clients ask you to confirm first.
Triggers validate_graph_agent. Nothing is saved.
Triggers send_graph_agent_event. The agent only reacts if the node it’s on has a payment_completed event edge.

Calls & executions

Triggers start_outbound_call — spends account balance, most clients ask you to confirm first.
Triggers stop_call.
Triggers list_agent_executions.
Triggers get_execution.
Triggers get_execution_raw_logs.

Batches

Triggers create_batch.
Triggers schedule_batch — starts real calls and spends balance, most clients ask you to confirm first.
Triggers get_batch.
Triggers list_batch_executions.
Triggers stop_batch.
Triggers delete_batch — irreversible, most clients ask you to confirm first.

Dispositions

Triggers list_dispositions.
Uses the Bolna MCP server’s built-in design_extraction prompt — no skill install needed. Produces a complete category/name/prompt/answer-value design, following the same methodology as the bolna-extraction-designer skill (see Skills Reference), ready to hand to create_disposition.
Triggers create_disposition.
Triggers bulk_create_dispositions.
Triggers test_dispositions.
Triggers update_disposition. Ask to delete one and it triggers delete_disposition instead — irreversible, most clients ask you to confirm first.

Knowledgebase (RAG)

Chains create_knowledgebase → get_knowledgebase to check status.
Chains list_knowledgebases → get_knowledgebase.
Triggers delete_knowledgebase — irreversible, most clients ask you to confirm first.

Phone numbers & inbound

Triggers list_phone_numbers.
Triggers search_phone_numbers.
Triggers buy_phone_number — spends account balance ($5/month), most clients ask you to confirm first.
Triggers setup_inbound_agent.
Triggers delete_phone_number — irreversible, most clients ask you to confirm first.

SIP trunks

Triggers create_trunk, with the gateway and carrier IP in the same call.
Triggers get_trunk_connection_details.
Chains list_trunks → get_trunk.
Triggers add_number_to_trunk with the agent set. Ask to move the number to another agent and it triggers assign_trunk_number_agent; ask to remove it and it triggers remove_number_from_trunk.
Chains start_trunk_test_call → get_trunk_test_call. Ask to test inbound instead and it chains arm_trunk_inbound_test → get_trunk_inbound_test, answering your next call to the trunk with an echo.
Triggers list_trunk_calls.
Triggers delete_trunk — irreversible, most clients ask you to confirm first.
Legacy SIP trunks (deprecated) are managed with their own tools; see the Tool list.

Sub-accounts

Triggers create_sub_account.
Triggers list_sub_accounts.
Chains list_sub_accounts → list_agents with the returned key passed as api_key — no reconnecting needed. See Calling tools with a different account.
Triggers get_sub_account_usage.
Triggers get_all_sub_accounts_usage.
Triggers delete_sub_account — irreversible, most clients ask you to confirm first.

Voice & providers

Triggers list_providers.
Chains list_tts_providers → list_voices.
Triggers remove_provider — breaks any agent still using it, most clients ask you to confirm first.

Violations

Triggers list_violations. Ask for a different status (“accepted”, “rejected”, “submitted”) and it filters accordingly.

Account

Triggers get_user_info.

Documentation

Triggers search_docs.
Chains search_docs → get_doc.

Chained, multi-step

These touch more than one tool in a single request — the assistant chains the lookups itself.
Chains list_agent_executions → get_execution.
Chains get_user_info → start_outbound_call.
Chains list_agents → get_agent per agent.
Chains list_agents → delete_agent; expect a confirmation prompt per delete.
Chains search_phone_numbers → buy_phone_number → setup_inbound_agent; expect a confirmation prompt before the purchase.

MCP overview

How the server works and what you can do with it

Example: Monitoring dashboard

Use these prompts to explore your data, then have your assistant build a small dashboard around it