Atlassian Rovo

Add a comment to a Jira issue, or edit an existing comment. Omit commentId to add a new comment; provide commentId to edit that comment. Comment text (commentBody) supports markdown. To edit, first get the commentId via getJiraIssue with comment fields.

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).

Returns the accountId of the current user

Create a new Confluence page, blog post, live doc, whiteboard, database, embed, smart link, or folder. Before authoring a body, call getContentFormatGuide through execute with name=getContentFormatGuide and inputs={toolName}. Use createConfluencePage for pages, blog posts, and live docs; createConfluenceWhiteboard for whiteboards; or createConfluenceDatabase for databases. Space instructions are durable guidance configured for a Confluence space. When present, they are authoritative and override authoring defaults on conflict. Follow this decision rule: 1. Before authoring, call getConfluenceSpace for the target space unless getConfluenceContent returned metadata.hasSpaceInstructions=false for content in that space. If getConfluenceSpace already returned for the same cloudId and space during the current task, reuse its spaceInstructions and do not call it again. 2. When the value is true or unknown and instructions have not been loaded, you must call getConfluenceSpace once before authoring through execute with name=getConfluenceSpace, top-level cloudId, and inputs={spaceIdOrKey}. 3. Apply any returned spaceInstructions. If a successful response omits them, no instructions are configured; author with defaults and do not block. After a successful getConfluenceSpace call, do not make a separate getConfluenceSpaceInstructions call.

Create a new Jira issue. Put custom fields in additional_fields, keyed by field name or customfield_* ID; values are resolved automatically, so no field lookup is needed first. A rejected create returns the required fields and their allowed values, so retry from that.

Find Atlassian operations that are not already in your tool list. Searches ~227 operations across Jira, Confluence, Compass, Bitbucket, Focus, Goals, Projects, Loom, Teams. Returns up to 5 matches with the exact name and inputs needed to call the matching execute-family tool (executeRead, executeWrite, or executeDestructive), then a briefer name-and-summary list of further matches — re-query with narrower terms to get one of those in full. Read all 5 before choosing. Only use an operation name from discover results or one already in your tool list; never guess, assume, or invent a name — when unsure, call discover first.

Edit an existing Jira issue; only fields editable on this issue can be set. Clear a field by passing explicit null, e.g. {"resolution": null}. Put custom fields in additional_fields, keyed by field name or customfield_* ID; values are resolved automatically, so no field lookup is needed first.

Run a destructive Atlassian operation by name (deletes or irreversibly changes data) across all Atlassian products. Only use an operation name from discover results or one already in your tool list; never guess, assume, or invent a name — when unsure, call discover first. If the user provides a Jira/Confluence URL, pass it directly as cloudId — no need to call getAccessibleAtlassianResources. Pass all inputs as a flat object — the server routes each to the right location (path, query, or body) automatically. Use responseFields for field filtering, e.g. ["key","fields.summary","fields.status.name"]. Use view to select a named output preset (e.g. "compact", "evidence", "full") when the operation supports views.

Run a read-only Atlassian operation by name across all Atlassian products. Only use an operation name from discover results or one already in your tool list; never guess, assume, or invent a name — when unsure, call discover first. If the user provides a Jira/Confluence URL, pass it directly as cloudId — no need to call getAccessibleAtlassianResources. Pass all inputs as a flat object — the server routes each to the right location (path, query, or body) automatically. Use responseFields for field filtering, e.g. ["key","fields.summary","fields.status.name"]. Use view to select a named output preset (e.g. "compact", "evidence", "full") when the operation supports views.

Run a write Atlassian operation by name (creates or updates data, non-destructive) across all Atlassian products. Only use an operation name from discover results or one already in your tool list; never guess, assume, or invent a name — when unsure, call discover first. If the user provides a Jira/Confluence URL, pass it directly as cloudId — no need to call getAccessibleAtlassianResources. Pass all inputs as a flat object — the server routes each to the right location (path, query, or body) automatically. Use responseFields for field filtering, e.g. ["key","fields.summary","fields.status.name"]. Use view to select a named output preset (e.g. "compact", "evidence", "full") when the operation supports views.