update_knowledge_chapter

Rewrite one existing chapter: its title, its body, or both. The body is REPLACED, never appended to - read the chapter with list_knowledge first and send the complete new text, not just the sentence you want to add. Returns what the text was before, so you can tell the human exactly what changed.

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":"update_knowledge_chapter","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","chapter_id":"3f9a…","body":"Mon-Sat 09:00-20:00, closed Sunday. Ramadan: 10:00-17:00."}}}'

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

{
  "chapter": {
    "id": "3f9a…",
    "title": "Opening hours"
  },
  "previous": {
    "title": "Opening hours",
    "text": "Mon-Sat 09:00-18:00, closed Sunday."
  }
}

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