Add or update a comment on a Jira issue

Adds a relationship between two entities in the Teamwork Graph (e.g. linking two Jira work items, marking one as blocking another, attaching a remote link, or connecting a Jira work item to an Atlas project or goal).

Add or update a worklog on a Jira issue. When worklogId is provided, updates that worklog;

Get current user info

Create a new Compass component

Create a relationship between Compass components

Create a custom field definition in Compass

Create a footer comment on a page or blog post

Create an inline comment on specific text in a page or blog post. For top-level comments, provide pageId and inlineCommentProperties (text selection + match counts). For replies, provide parentCommentId only (no pageId or inlineCommentProperties). You must first fetch the page content (e.g. using getConfluencePage) to find the exact text and count how many times it appears. Incorrect or missing inlineCommentProperties can result in a 400 error from the Confluence API.

Create a Confluence page or blog post. When contentFormat is "html" or omitted because HTML is the default, first call the getContentFormatGuide tool with { toolName: "createConfluencePage" } and follow the returned HTML-format guidance. Do not call it when contentFormat is "markdown".

Create a link between two Jira issues. For directional link types (e.g. Blocks): inwardIssue = issue that blocks, outwardIssue = issue that is blocked (e.g. "A is blocked by B" → inwardIssue: B, outwardIssue: A). Use getIssueLinkTypes if link type is unknown.

Create a Jira issue. Use additional_fields to set any Jira field that does not have its own parameter (e.g. custom fields, priority, components).

Update issue. After updating, returns the issue using the same default read fields as getJiraIssue (summary, description, status, issuetype, priority, labels, components, assignee, reporter, created, updated, resolution, project). Use getJiraIssue with fields ["*all"] or a custom list if you need more.

Get details of a Jira issue or Confluence page by ARI (Atlassian Resource Identifier), if the id is not an ARI, then use a different tool to fetch the content

Get cloudId to make tool calls. When a link is provided (e.g. https://site.atlassian.net/*), try passing the site hostname (e.g. site.atlassian.net) as cloudId to other tools first; if that fails, use this tool to list accessible resources.

Get a Compass component by ID

Get a list of Compass components

Get a list of Compass custom field definitions

Get reply(child) comments for a comment

Get a Confluence page or blog post by ID, including body content.

Get child pages of specified page

Get footer comments for a page or blog post

Get inline comments for a page or blog post

Get spaces

Get the canonical Confluence HTML-format guidance for `createConfluencePage` or `updateConfluencePage`. Use this tool before authoring HTML/default page bodies or fine-grained HTML edits. First call with only `toolName`; if the returned guidance references a follow-up document, call this tool again with the same `toolName` and `reference` set to that single referenced path. Fetch one document per call. Valid `toolName` values: createConfluencePage, updateConfluencePage.

Get available Jira issue link types (e.g. Blocks, Duplicate, Clones, Relates). For createIssueLink: inwardIssue = blocker, outwardIssue = blocked (e.g. "A is blocked by B" → inwardIssue: B, outwardIssue: A).

Get issue details

Get remote links

Get field metadata

Get issue types

Get pages or blog posts in a space

Retrieves connected context from Teamwork Graph for any Atlassian entity. Returns all relationships and linked objects within one traversal – including cross-product and third-party connections. Use when the answer requires connections between entities, not just a single entity's fields. Supported entry points: Jira: issues, projects, sprints, versions, comments Confluence: pages, blogposts, whiteboards, databases, spaces Goals, Projects, Focus Areas, Tags and updates People: users, teams, organisations DevOps: PRs, repos, deployments, services, builds, designs Loom: videos, meetings Compass: components Assets: objects Incidents, conversations, calendar events, external documents After calling this tool, call getTeamworkGraphObject on returned ARIs to get full content. The utilisation of this tool may consume up to 10 Rovo Credits. If the user or organization does not have any Rovo Credits available, the tool call will fail.

Fetches the entire available data for one or more objects (Atlassian or third-party) using their ARIs or URLs. Use for the objects gathered from getTeamworkGraphContext tool.

Get transitions

Get projects

Lookup user IDs

Search Jira, Confluence and linked 3P data using Rovo Search, ALWAYS use this tool to search for Jira and Confluence content unless the word CQL or JQL is used in the context. The utilisation of this tool may consume up to 10 Rovo Credits. If the user or organization does not have any Rovo Credits available, the tool call will fail.

Search Confluence content (pages, blog posts, comments, attachments) using CQL (Confluence Query Language). CQL is specific to Confluence and is not interchangeable with JQL.

Search issues with JQL, total counts only when explicitly requested.

Transition issue status

Update a Confluence page or blog post. When contentFormat is "html" or omitted because HTML is the default, first call the getContentFormatGuide tool with { toolName: "updateConfluencePage" } and follow the returned HTML-format guidance. Do not call it when contentFormat is "markdown".