apiwatch

All changes / Atlassian Rovo MCP

Breaking mcp

Rovo MCP stopped returning the legacy Loom video tools to the Loom V2 rollout cohort; V2 Loom Object tools replace them

Took effect · Rovo MCP Loom tools (read_loom / write_loom) V1 video tools → V2 Loom Object tools

Reviewed against the vendor source on Oct 29, 2026 (AI-assisted review). Key facts are re-checked against the source daily.

What changes

Atlassian's changelog (CHANGE-3504, dated 23 Oct 2026) says that as of October 16, 2026 the legacy Loom MCP tools are no longer returned to users in the Loom V2 rollout cohort, and lists V2 replacements (CHANGE-3503 announces the consolidated Loom Object tool surface). This applies per rollout cohort: users outside the V2 cohort continue to receive the V1 tool surface until their cohort moves to V2, so the date a given account loses the old tools can be later. getLoomVideo is unlisted rather than immediately disabled: it is no longer advertised in tools/list or discover, but an existing session that cached its schema can keep calling it by exact name during a compatibility period, and a later cleanup change will remove it. The other replaced operations, which use the discover and execute flow, are removed from the enabled operation list for each V2 cohort. getLoomVideoDownloadUrl and recoverLoomVideo are not replaced by this migration. The tools stay in the read_loom and write_loom permission groups.

Breaking: Calls fail after this date.

What to do

Switch to the V2 names the changelog gives: listLoomVideos and listLoomVideosSharedWithMe → listLoomObjects; getLoomVideo → getLoomObjectsContent; getLoomVideoComments and getLoomMeetingActionItems → getLoomObjectsContent with the applicable content expansion; createLoomVideoComment and createLoomVideoReaction → addLoomInteraction; updateLoomVideoTitle → updateLoomObjectMetadata; updateLoomVideoPermissions → updateLoomObjectVisibility; shareLoomVideo → shareLoomObject; createLoomVideoUpload → createLoomObjectUpload; publishLoomVideo → publishLoomObject; listLoomFolders → listLoomObjectFolders; createLoomFolder → createLoomObjectFolder; moveLoomVideoToFolder → moveLoomObjectToFolder. Keep getLoomVideoDownloadUrl and recoverLoomVideo. Because rollout is per cohort, read tools/list (and discover, for operations called through execute) at startup and use whichever set the server advertises.

Strings to search for

listLoomVideoslistLoomVideosSharedWithMegetLoomVideogetLoomVideoCommentsgetLoomMeetingActionItemscreateLoomVideoCommentcreateLoomVideoReactionupdateLoomVideoTitleupdateLoomVideoPermissionsshareLoomVideocreateLoomVideoUploadpublishLoomVideolistLoomFolderscreateLoomFoldermoveLoomVideoToFolder

Source

https://dac-changelogs.services.atlassian.com/changes?apiGroups=rovo-mcp&limit=15&match=CHANGE-3504