They answer the question a dashboard cannot: not what did I spend, but which bot, model or ad is costing more than it is worth.
Real prompts, not pseudo-code. Claude picks the tools itself.
| Tool | Needs | What it does |
|---|---|---|
get_bot_costs | read | Spend per bot, with cost per reply and the model breakdown. |
get_credit_balance | read | Credits and AI replies left this month, per workspace. |
get_ad_results | read | Chats, leads, sales and spend per Click-to-WhatsApp ad, with the cost of each. |
get_meta_conversions | read | Whether sales from ads reach Meta, and which ad conversations were reported as a Purchase. |
set_meta_purchase_stage | write | Mark a pipeline stage as a sale, so ad leads who reach it are sent to Meta as a Purchase. |
set_meta_tracking | write | Connect a WhatsApp number to the Meta dataset, so ad leads and sales are reported to Meta. |
list_feedback | read | Bug reports your team has sent from inside the console — what broke, who hit it, and which are still open. |
read works with any key. write is refused unless the key allows it — the server checks before the tool runs, so a read-only key genuinely cannot change anything.
Worth knowing before you wire it into something that matters.