Sales tools by domain

The Sales-Management MCP can expose one focused Sales Platform domain or the combined tool set. Use this map to pick the smallest domain for the task; open the full reference only when you need exact parameters, result shapes, pagination, or write semantics.

Use this surface from Claude or Codex during configuration and prototyping. After a workflow is promoted, the Agents routine reaches the same domain through the Sales connector or tool enabled on its executing agent. See the routine-first operating model.

Task	Domain	Full reference
Configure sales assistants, instructions, skills, available tools, and test chats; view and patch long instructions and skills, list their versions, and restore one; behaviour and hand-off settings, Work Hours, Flight Control, control numbers, and live notes; the model an assistant answers with and its price	sales_assistants	Assistants
Page through clients, manage leads, context, notes, tasks, attachments, labels, and pipeline stages; list the team and custom lead fields, find and merge duplicate leads, change many leads' status, labels, or manager at once, and rename, recolor, or move a status	sales_clients	Clients, leads, and pipelines
Page through chats and retrieve bounded message history	sales_conversations	Conversations
Inspect or configure messaging and voice channels, and a channel's reply delay and reaction handling	sales_channels	Channels
Configure follow-ups and attach or detach them on an assistant, preview an audience, send a one-off message, schedule a message or call to one lead for a later time, or place an outbound call	sales_outreach	Outreach and follow-ups
Manage FAQ knowledge and product integrations; add documents from a link, check each source's indexing status, re-index one, and test what an assistant's knowledge finds	sales_knowledge	Knowledge Base
Inspect connected third-party integrations and obtain configuration links; edit one trigger of a live automation such as a Trigger Outreach campaign (preview first, then confirm); create, change, and attach API Actions; get the dashboard link to connect a CRM, Google Sheets orders, Google Calendar or a Custom MCP server, check a connection with its stored credentials, attach or detach one, and connect a Custom MCP server and choose its tools	sales_integrations	Integrations
Inspect account, subscription, token, and usage summaries	sales_account	Account and usage
List orders, retrieve one order, and aggregate order statistics	sales_orders	Orders
List calendar events, staff, services, and aggregate statistics; set up the built-in Calendar — its settings, staff, services and their working hours — and create, move or cancel a booking	sales_calendar	Calendar
Inspect and map Meta lead forms; pause and resume an automation; create and delete Trigger Outreach triggers; set up an assistant's Keyword Responder and Lead Form Instant Outreach	sales_automations	Automations
Save conversations as eval scenarios and run instruction comparisons	sales_evals	Testing and evals

Pagination belongs to the caller

List and scan tools expose bounded pages with filters, limits, offsets or cursors where documented. For a large dataset, the routine or skill script should request a page, process it, advance the pagination state, and stop at an explicit total or completion condition. Do not treat an export-style name as permission to request every client or chat in one server call.

For example, an archive routine can page through chats, call get_chat_messages with a per-chat message limit (following next_before while has_more is true to read a long chat in full), append normalized rows to its working CSV, and publish the final artifact only after all pages are complete. The script owns the total-record loop; each MCP call stays bounded and retryable.

Edit long instructions and skills

Change part of an assistant's instructions or a skill without resending the whole text: assistant_view_instructions and assistant_view_skill read an outline, a section, a line range, or search hits, in the whole text or within a section or line range; assistant_patch_instructions and assistant_patch_skill apply exact edits, with dry_run for a diff first; assistant_list_instruction_versions, assistant_list_skill_versions, assistant_restore_instructions, and assistant_restore_skill list and bring back earlier versions, deleted skills included. See Edit long instructions and skills safely.

Settings, hours, and Flight Control

assistant_get_settings and assistant_update_settings read and change an assistant's behaviour and hand-off settings (manager mode, the hand-off stop word, auto-return, link handling, reply language, web search, communication guidelines) with the dashboard's own checks and a before/after answer. assistant_get_working_hours and assistant_set_working_hours read and set Work Hours. assistant_get_flight_control shows whether a Telegram group gets Flight Control updates and the link that connects one; control numbers and live notes have list, add, and remove tools. In sales_channels, set_channel_options sets a channel's reply delay and reaction handling; in sales_integrations, api_action_create, api_action_update, and api_action_attach manage API Actions without ever touching their header values. See Assistant settings, hours, and Flight Control from Claude or Codex.

Lead structure, knowledge sources, and models

In sales_clients, list_managers lists the team a lead can be assigned to, and list_lead_fields, lead_field_create, lead_field_update, and lead_field_delete manage the lead card's custom fields. list_duplicate_clients finds pairs of leads that are one person and client_merge merges a pair, which cannot be undone. client_bulk_update changes the status, labels, or manager of many leads, by id or by filter, after a dry run that shows the count and a sample. funnel_status_update renames, recolors, or moves a status; a rename reaches every lead of that pipeline that has it. In sales_knowledge, add_document_knowledge adds a PDF, DOCX, TXT, or CSV file from an https link, list_knowledge_sources shows each source's indexing status, refresh_knowledge_source re-indexes one, and test_knowledge_search shows what an assistant's knowledge finds for a question. In sales_assistants, assistant_get_model shows the model an assistant answers with, where it comes from, and its price.

Connecting integrations

In sales_integrations, credentials never pass through a tool: API keys, header values and sign-ins are entered by the owner in the dashboard. integration_setup_link gives the link to one card on one assistant and says whether the plan or another integration blocks it. integration_verify checks a connected CRM, Google integration or Custom MCP server with what is stored, without changing it. integration_attach and integration_detach put a connected CRM, Custom MCP server, Spreadsheet Orders or Google Calendar on another assistant, or take it off one. custom_mcp_create connects a Custom MCP server by its URL (one that needs headers is saved with no tools on for the owner to finish), and custom_mcp_set_tools chooses its tools. Writes preview before confirm: true.

Setting up the built-in Calendar

In sales_calendar, calendar_get_settings and calendar_get_staff_hours read the built-in Calendar's settings and a member's weekly hours. calendar_update_settings and calendar_set_staff_hours change them; calendar_staff_create, calendar_staff_update, calendar_staff_delete and the three calendar_service_* tools manage staff and services (removals are refused while bookings are to come). calendar_booking_create and calendar_booking_update book, move or cancel a customer's appointment without notifying them. Every write previews before confirm: true.

Pausing automations and attaching follow-ups

In sales_automations, automation_set_paused pauses or resumes a Trigger Outreach, Keyword Responder, Lead Forms, or Lead Form Instant Outreach automation without deleting it. While paused, queued sends are dropped and nobody is messaged; a paused Lead Forms automation still captures leads into Contacts, and nothing is replayed on resume. In sales_outreach, assistant_attach_follow_up attaches a postponed sequence to an assistant — a live one then messages that assistant's matching leads on its schedule — and assistant_detach_follow_up detaches it, keeping the sequence; chats already part-way through keep their queued steps until it is unpublished. All three preview the change and apply it only with confirm: true.

Setting up automations

In sales_automations, create_integration_trigger adds a Trigger Outreach webhook trigger to an assistant (creating its automation when needed) and returns the webhook URL, a credential to give only to the system that calls it; delete_integration_trigger removes one for good. set_keyword_responder creates or changes an assistant's Keyword Responder, with posts picked from list_social_posts, and set_lead_form_instant_outreach creates or changes a Lead Form Instant Outreach automation. Each previews the change, applies it only with confirm: true, and runs as soon as it is saved.

Effects and testing

Read operations touch real connected systems and are appropriate for capability checks. Messages, calls, deletions, and live record changes are external effects: test them on a controlled record or recipient, require stable identifiers and idempotency where possible, and keep automation disabled until the effect and recovery path are accepted.

Complete reference for agent clients

Every tool, parameter, default, result, and error is documented in Sales tools reference. Its canonical raw Markdown is available at https://docs.mychatbot.app/mcp/sales-tools-reference.md.

See also

• Agents Platform operating model — configuration plane and production Sales access
• MCP at MyChatBot — choose the correct server
• Sales Platform MCP — address, access key, areas, and client setup
• Process hundreds of records — bounded foreach pattern
• Routine workflow map — choose the right control-flow construct