x

apps/mcp-server/README.md

@@ -32,7 +32,37 @@ bun run dev
 
 - `update_brand_name` เปลี่ยนชื่อแบรนด์กลางที่ใช้ใน header/footer ของ `apps/spa` และ `apps/website`
 - `update_store_settings_translation` อัปเดตข้อความแปลของ store settings
-- `update_footer_content` อัปเดตเนื้อหา footer และลิงก์ที่เกี่ยวข้อง
+- `update_footer_content` อัปเดตคำอธิบายแบรนด์และ social links เท่านั้น
+
+## Footer Menu LLM Workflow
+
+Footer Explore and Footer Support are flat item menus, not Mega Menu payload trees. Supported menu names are:
+
+```text
+footer-explore
+footer-support
+```
+
+Use this workflow for every Footer menu edit:
+
+1. Call `get_footer_menu` with the target language.
+2. Keep the returned `version`.
+3. Call one item-level write tool with `dryRun: true` and `expectedVersion`.
+4. Review the compact preview.
+5. Apply the same operation with `dryRun: false` and the same version.
+6. Call `get_footer_menu` again to verify and obtain the next version.
+
+Available item-level tools:
+
+- `add_footer_menu_item`
+- `update_footer_menu_item`
+- `delete_footer_menu_item`
+- `reorder_footer_menu_items`
+- `update_footer_menu_item_translation`
+
+Every reorder request must include every current item ID exactly once. A `MENU_VERSION_CONFLICT` response means Admin or another agent changed the menu after it was read; fetch it again before retrying.
+
+Do not pass `exploreLinks`, `collectionLinks`, or `supportLinks` to legacy `update_footer_content`. Full menu-array replacement is rejected because it can delete item IDs and translations. Website Collections are populated from Categories rather than a `footer-collections` menu.
 
 ## Mega Menu LLM Workflow