delete_knowledge_chapter

Remove one chapter so the AI stops answering from it. Restorable for 7 days with restore_knowledge_chapter; after that it is gone. Confirm with the human before calling this - a deleted chapter is a fact the AI can no longer answer, and callers will hear "I do not know" where they used to hear the answer.

This is the exact text the model reads before deciding to call.

curl -X POST https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"delete_knowledge_chapter","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","chapter_id":"58b1…"}}}'

The result arrives as an MCP content block; the JSON below is what the text field parses to.

{
  "deleted": true,
  "title": "Parking",
  "restorableDays": 7
}

Every request carries Authorization: Bearer avk_…. Create a key in the Avrosh dashboard under Docs; it is shown once, because only its hash is stored.

One key reaches every business on the account that made it, and no others. There are no scopes to configure and nothing to switch on — a connected assistant receives the whole toolset. What bounds it is whose account the key belongs to, which is enforced in the database rather than by a permission anybody sets.

curl https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY"

list_businesses · get_business · list_calls · get_transcript · create_business · update_business · list_knowledge · add_knowledge_chapter · update_knowledge_chapter · delete_knowledge_chapter · restore_knowledge_chapter · list_menu_items · create_menu_item · update_menu_item · set_menu_item_availability · delete_menu_item · restore_menu_item · remove_menu_item_photo · set_menu_item_thumbnail · list_bookable_types · create_bookable_type · update_bookable_type · set_bookable_type_schedule · delete_bookable_type · restore_bookable_type · list_bookings · get_booking · confirm_booking · cancel_booking · list_work_queue · accept_order · finish_order · accept_request · finish_request · assign_request · list_customers · get_customer · export_customer_data · erase_customer