Update from code changes: document admin MCP navigationErrors

[mintlify]

Summary

The admin MCP node tools create_node, update_node, move_node, and delete_node now return a navigationErrors field when a write leaves the navigation invalid. One example is a page placed at the root next to tabs. Mintlify can leave invalid nodes out of the published navigation. This field gives the AI a chance to fix the problem before it calls save.

Triggered by https://github.com/mintlify/server/pull/8654

Changes

• Added a short paragraph about navigationErrors to the Navigation tools section of the admin MCP page.
• Added the same paragraph to the es, fr, and zh versions of the page.

Context

This only warns the AI. Publishing and save are still not blocked when the navigation has errors.

---

Note

Low Risk
Documentation-only updates to MCP reference pages; no runtime or API behavior changes in this repo.

Overview
Documents the navigationErrors response field on admin MCP navigation write tools (create_node, update_node, move_node, delete_node) in the Navigation section of mintlify-mcp.mdx.

The new paragraph explains that invalid nav layouts (e.g. a page at the root beside tabs) return navigationErrors, that published nav may omit invalid nodes, and that agents should fix those issues before calling save. The same addition is mirrored in es, fr, and zh locale pages.

^{Reviewed by Cursor Bugbot for commit bbcf712. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
mintlify	🟢 Ready	View Preview	Sep 28, 2026, 6:06 PM