Loom MCP tools are moving to a consolidated recording workflow

Atlassian Rovo MCP is migrating Loom recording workflows to a consolidated V2 Loom Object tool surface.

Loom objects currently include async videos and meeting recordings. The new tools use consistent object-based names so that Loom can support more content types without another tool migration.

For each rollout cohort, the V2 tools replace the corresponding V1 tools. The MCP server will advertise only the applicable V2 replacement operations.

V2 capabilities

The V2 tools support:

• Loom ARIs, share URLs, and embed URLs as recording identifiers.
• Async videos and meeting recordings through the same tool contracts.
• Consolidated comments and reactions.
• Batch retrieval with one result per requested recording.
• Explicit recording and content-component statuses.
• Transcript, agent brief, action item, comment, attached-link, and developer-log retrieval.
• Consistent folder operations for Loom objects.

Replacement map

• listLoomObjects replaces listLoomVideos and listLoomVideosSharedWithMe.
• getLoomObjectsContent replaces getLoomVideo for supported metadata, transcripts, agent briefs, action items, comments, attached links, and developer context logs.
• addLoomInteraction replaces createLoomVideoComment and createLoomVideoReaction.
• updateLoomObjectMetadata replaces updateLoomVideoTitle and also supports description updates.
• updateLoomObjectVisibility replaces updateLoomVideoPermissions.
• shareLoomObject replaces shareLoomVideo.
• createLoomObjectUpload replaces createLoomVideoUpload.
• publishLoomObject replaces publishLoomVideo.
• listLoomObjectFolders replaces listLoomFolders.
• createLoomObjectFolder replaces createLoomFolder.
• moveLoomObjectToFolder replaces moveLoomVideoToFolder.

Permission groups

The tools remain in the existing read_loom and write_loom permission groups. This migration does not add a new organization-admin permission.

Tools that remain available

The following operations are not replaced by this migration:

• getLoomVideoDownloadUrl
• recoverLoomVideo

Rollout and compatibility

Availability will move through rollout cohorts. Users outside the V2 cohort will continue to receive the V1 tool surface until their cohort moves to V2.

getLoomVideo is a high-frequency tool whose schema may be cached by MCP clients. During its deprecation period, the server will stop advertising it in tools/list and discover. However, an existing client with the cached tool can continue to call it by its exact name. This prevents active sessions from failing while new and refreshed sessions move to getLoomObjectsContent.

The other replaced V1 operations use the discover and execute flow. They will be removed from the enabled operation list for each V2 cohort.

The team will monitor calls to the unlisted getLoomVideo operation. A later cleanup change will remove the old operation and its supporting action after cached usage reaches an agreed safe level.

For details about these tools and other tools available in the Atlassian Rovo MCP Server, see the supported-tools documentation.