Description

Currently, the Atlassian/Rovo MCP update_page tool requires the model to supply the entire page body on every update. For large or continuously growing pages (e.g. on-call runbooks, rolling meeting agendas), this is extremely wasteful, it burns a large portion of the model's context window just to append a single line or update one section.
Expected behaviour: The MCP tool should expose a mechanism for targeted/incremental updates, for example:

•  Append content to the end of a page
•  Replace a specific named section or heading block
•  Insert content before/after a known anchor