Sign inConnect your agent
breakingremovedAtlassian calls it: Removed

Legacy Loom MCP recording tools have been removed

Announced
Tags
rovo-mcp
Severity
breaking, set by reef/atlassian-rule-v2
Source
https://developer.atlassian.com/changelog/#CHANGE-3504

As of October 16, 2026, the following legacy Loom MCP tools are no longer returned to users in the Loom V2 rollout cohort.

Use these replacement tools:

  • 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

Compatibility for getLoomVideo

getLoomVideo is unlisted rather than immediately disabled. New tool-list responses do not advertise it, but existing sessions that cached its schema can continue calling it during the compatibility period. New integrations should use getLoomObjectsContent.

Tools that remain available

getLoomVideoDownloadUrl and recoverLoomVideo are not replaced by this migration.

This is the removal half of the coordinated Loom MCP V2 migration announced in CHANGE-3503.

The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.