Why was ConfluenceDatabaseEditTool available during one successful Rovo operation, but unavailable i

Jo Heylen

Why was ConfluenceDatabaseEditTool available during one successful Rovo operation, but unavailable in subsequent attempts?

Rovo successfully updated two fields in an existing Confluence Database. We confirmed that the changes were saved in the database, and the execution message referenced ConfluenceDatabaseEditTool.

Subsequent attempts using essentially the same prompt failed, including with the database open and selected as the active context. Rovo now reports that this tool is unavailable.

Could someone clarify:

• Under what conditions is ConfluenceDatabaseEditTool available?
• How can we reliably activate it for an existing database?
• Could a rollout or platform change explain this difference?

Tests performed on 13 October 2026.

We need a reproducible way to update existing database rows using Rovo.

Sami Shaik

@Jo Heylen ,
I cannot give you the activation conditions for ConfluenceDatabaseEditTool, because Atlassian does not document the tool by that name anywhere I can find; it is an internal tool name that leaked into an execution message. What is documented tells you most of what you need, though.

The capability is still Beta and still rolling out. Atlassian’s release note “Create and edit databases instantly with Rovo” lists Status Rolling Out, Change impact Beta, rollout “starting in December 2025”, with two key changes: “Ability to create new databases in Confluence using Create with Rovo” and “Ability to edit existing databases by chatting with Rovo.” A feature in that state can be present for one request and absent for the next on the same site, which is consistent with what you saw on 13 October. Whether the switch is per tenant, per user or per conversation is not published, so I will not guess.

The documented entry point is not the chat box with the database open. The release note’s getting-started steps go through Create, then Create with Rovo, create the database from a prompt, then edit it. Editing by chat is listed as a capability, but no page states that an existing, non-Rovo-created database selected as context will expose the edit tool, so “database open and selected as active context” is not a documented trigger even though it worked once.

If you need reproducible row updates today, use the agent path that is API-backed. On 7 July 2026 Atlassian announced that Confluence Databases are supported in Atlassian MCP v2 Preview and the TWG CLI: agents such as Rovo Dev, Claude or Codex can “create, read, and edit Whiteboards and Databases” through those tools. That is a defined tool surface rather than a chat capability behind a rollout flag, which is what “reproducible” needs. It is also Preview, so it belongs in a pilot, not a production workflow yet.

What to send Atlassian. Both execution messages (the one naming the tool and the one saying it is unavailable), the timestamps, the site, and whether the database was created by Rovo or by hand. That is the reproduction Support can take to the Rovo team; the Community cannot read the flag state.

References:

• Release note, Create and edit databases instantly with Rovo: https://community.atlassian.com/release-notes/2iJtMirRtLgZyA5jIUYBr3
• Whiteboards and Databases in MCP v2 and CLI (Atlassian Team, 7 Jul 2026):
  https://community.atlassian.com/forums/discussion/3258701/whiteboards-and-databases-are-now-supported-in-atlassian-mcp-v2-and-cli