Atlassian Remote MCP connector tools

  • Updated

The Atlassian connector tools in Opal lets Opal interact directly with your Jira, Compass, Confluence environments. Opal can help you manage your projects, tasks, and documentation without you having to switch between applications.

First, an Opal administrator must add the Atlassian Remote MCP to Opal. After adding the MCP server, individual Opal users and agent builders can log in to Atlassian to access their information from Opal. Administrators only need to add the Atlassian Remote MCP once.

Add Atlassian Remote MCP to Opal

  1. Go to Tools > Connectors in Opal.
  2. Click Add Remote MCP.
  3. Click Atlassian.

  4. Click Next.

  5. Click Connect to Atlassian.

  6. Complete required access configuration and click Accept.

The Atlassian MCP tile now displays on the Connectors tab for users to authenticate with their personal accounts.

User-level auth for Atlassian

After an administrator adds Atlassian Remote MCP to Opal, you can log in from Opal to access your information. User-level authorization ensures individual Opal users and agent builders can only access data they have permission to access within Atlassian.

To authenticate, complete the following steps in Opal:

  1. Go to Tools > Connectors.
  2. Click Connect for Atlassian.
  3. Log in to Atlassian

After you connect to Atlassian, the Atlassian connector tools become available in Opal Chat, agents, and workflows.

Atlassian connector tools

After an administrator adds Atlassian Remote MCP to Opal and you log in to Atlassian using User-level auth for Atlassian, you can call the following tools in Opal. Click a tool's name to expand it and learn when to use the tool, required and optional parameters, and example prompts on how to call the tool. If you do not provide a required parameter, Opal prompts you for it.

Jira issue management

Use these tools to create, modify, and update the status of tasks and tickets within Jira projects.
createJiraIssue – Create new issues (Tasks, Bugs, or Stories) in a specific project.
  • When to use
    • Report a new bug discovered during testing or user feedback.
    • Create a task for a teammate to track specific action items.
    • Capture a new feature request or improvement as a Story.
    • Kick off a new sub-task within an existing parent issue.
  • Parameters
    • cloudId – Atlassian Cloud ID (UUID or site URL).
    • projectKey – Short key for the project (for example, PROJ).
    • issueTypeName – Name of the issue type (Task, Bug, or Story).
    • summary – Brief title of the issue.
    • (Optional) description – Detailed background or steps to reproduce.
    • (Optional) assignee_account_id – Account ID of the user to assign.
    • (Optional) parent – Parent issue key if creating a subtask.
  • Example prompts
    • Create a new Bug in the OPAL project with the summary "CSS alignment issue on mobile".
    • I need to track a task in project MKT: "Write email sequence for Spring campaign".
    • Can you create a Story for a new search feature in project DEV?
editJiraIssue – Update existing issue fields and details.
  • When to use
    • Refine an issue's description with more technical detail.
    • Update the assignee of a ticket as the project progresses.
    • Change priority levels based on shifting business goals.
    • Correct errors in the original issue summary.
  • Parameters
    • cloudId – Atlassian Cloud ID/Site URL.
    • issueIdOrKey – The ID or key of the Jira issue.
    • fields – A JSON string representing the fields to update.
  • Example prompts
    • Update the description of PROJ-123 to include the new design links.
    • Change the summary of BUG-789 to "Fixed: Login intermittent failure".
    • Edit Jira task TASK-456 to set the priority to "High".
transitionJiraIssue – Change the status of an issue (for example, moving from "In Progress" to "Done").
  • When to use
    • Move a task from "To Do" to "In Progress" when you start working on it.
    • Mark a bug as "Fixed" or "Resolved" once the code has been merged.
    • Transition a story to "Ready for Review" or "Testing" to notify stakeholders.
    • Reopen an issue that was previously closed if the problem resurfaces.
  • Parameters
    • cloudId – Atlassian Cloud ID (UUID or site URL).
    • issueIdOrKey – Unique ID or key (for example, PROJ-123) of the Jira issue.
    • transition – A JSON object or string specifying the transition ID or name to apply.
    • (Optional) fields – A JSON string of fields to update on the issue during the transition.
    • (Optional) update – Custom update operations to perform during the transition.
    • (Optional) historyMetadata – Metadata for the issue history entry created by the transition.
  • Example prompts
    • Move Jira ticket PROJ-101 to "Done".
    • Transition issue WEB-404 to "In Progress".
    • Set the status of FIX-123 to "Resolved" in my Jira project.
    • Can you reopen the Jira ticket TEST-789?
addCommentToJiraIssue – Adds a comment to an existing Jira issue.
  • When to use
    • Provide a progress update or status change directly on a Jira ticket.
    • Log meeting notes or external communication details related to a specific issue.
    • Ask a question or request feedback from a teammate within the context of a task.
    • Notify stakeholders of a resolution or a newly discovered blocker.
  • Parameters
    • cloudId – Atlassian Cloud ID (UUID) or site URL. 
    • issueIdOrKey – The unique ID or key (for example, PROJ-123) of the Jira issue.
    • commentBody – The text of the comment (Markdown supported).
    • (Optional) commentVisibility – Controls who can see the comment.
  • Example prompts
    • Add a comment to Jira issue PROJ-123 saying the deployment is complete.
    • Comment on Jira ticket WEB-456: "I've reviewed the PR and left some comments on Bitbucket".
    • Can you add a note to issue 10107 in Jira? "Waiting for the marketing assets".
addWorklogToJiraIssue – Log time spent on specific Jira tasks.
  • When to use
    • Record the hours spent developing a specific feature or component.
    • Log time for billable customer support or consulting tasks.
    • Track effort for internal reporting, sprint velocity, or resource planning.
    • Document time spent on manual testing or bug investigation.
  • Parameters
    • cloudId – Atlassian Cloud ID (UUID or site URL) for the Atlassian instance.
    • issueIdOrKey – Unique ID or key (for example, PROJ-123) of the Jira issue.
    • timeSpent – Duration of work (for example, 2h, 30m, 1d 4h). 
    • (Optional) commentBody – An optional description of the work performed.
    • (Optional) visibility – Optional setting to restrict visibility of the worklog.
  • Example prompts
    • Log 2 hours of work on Jira issue PROJ-123 with the note "Initial draft of the marketing brief".
    • I spent 45 minutes today on TAS-789, please log it in Jira.
    • Add a worklog to WEB-456: 1h 30m spent on debugging the registration form.
    • Log 3 hours against FIX-101 for manual testing effort.
jiraWrite – Performs write operations in Jira, primarily for creating relationships between issues.
  • When to use
    • Establishing dependencies between tasks, such as marking one issue as "blocking" another.
    • Streamlining project management by linking duplicate issues to a primary ticket.
    • Connecting related work across different Jira projects to maintain visibility for cross-functional teams.
    • Adding contextual comments automatically when a relationship between two issues is defined.
  • Parameters
    • action – The specific write operation to execute (for example, createIssueLink).
    • cloudId – The Atlassian Cloud ID (UUID or site URL).
    • inwardIssue – (Required for linking) The key of the inward Jira issue (for example, HSP-1).
    • outwardIssue – (Required for linking) The key of the outward Jira issue (for example, MKY-1).
    • type – (Required for linking) The name of the link relationship (for example Duplicate, Blocks, Clones, Relates).
    • (Optional) comment – A markdown-formatted comment to be added to the outward issue during the operation.
  • Example prompts
    • Link Jira issue PROJ-123 to PROJ-456 as 'relates to'.
    • This task PROJ-101 is blocked by PROJ-102. Can you update the link in Jira?
    • Mark Jira issue BUG-50 as a duplicate of BUG-40 and add a comment that the fix is already in progress.
    • Create a link between ABC-1 and ABC-2 with the type 'Clones'.

Jira information and metadata

Use these tools to retrieve detailed data about issues, project configurations, and available workflows.
getJiraIssue – Retrieves detailed information about a specific Jira issue.
  • When to use
    • Access the current status, description, and assignee of a specific bug, story, or task.
    • Retrieve full details of a Jira ticket to summarize its history or current progress for a report.
    • Check specific metadata such as labels, priority, or custom fields associated with a project key.
    • Verify the details of a development item before updating its status or adding a comment.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • issueIdOrKey (Required) – The ID or unique key of the issue (for example, "PROJ-123" or "10000").
    • (Optional) fields – A list of specific fields to include in the response.
    • (Optional) fieldsByKeys – Whether to refer to fields by their keys instead of IDs.
    • (Optional) expand – A comma-separated list of additional information to include, such as "renderedFields" or "names".
    • (Optional) properties – A list of specific issue properties to retrieve.
    • (Optional) updateHistory – Whether to add the issue to your "Recent Issues" history in Jira.
    • (Optional) failFast – Whether the request should fail immediately if an error occurs.
  • Example prompts
    • Show me the details for Jira issue PROJ-456.
    • What is the current status and assignee for the bug ticket WEB-102?
    • Retrieve the full information for Jira task MKT-789, including comments and priority.
    • I need to see the description and labels for Jira story DEV-555.
getJiraIssueRemoteIssueLinks – Retrieves remote issue links associated with a specific Jira issue.
  • When to use
    • Find external links attached to a ticket, for example, links to documentation, mockups, or related issues in other Jira instances.
    • Identify integrations between a Jira issue and external tools like Confluence, Bitbucket, or GitHub.
    • Check a ticket for specific global identifiers to track connections across multiple platforms.
    • Verify all external references for a task before marking it as complete or moving it through a workflow.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • issueIdOrKey– The ID or unique key of the issue, for example, "PROJ-123" or "10000".
    • (Optional) globalId – The unique identifier of the remote issue link to retrieve.
  • Example prompts
    • Show me all the remote issue links for Jira ticket PROJ-123.
    • Are there any external links or documentation connected to Jira issue WEB-456?
    • Retrieve the remote link details for Jira task MKT-789.
    • Find the external references for Jira story DEV-101 using its key.
getJiraIssueTypeMetaWithFields – Retrieves field metadata for a specific issue type within a project.
  • When to use
    • Identify the required and optional fields for a specific issue type, for example, "Bug" or "Story", before creating a new ticket.
    • Understand the data type and validation rules for custom fields to ensure correct input.
    • Check which fields are available for a task in a specific project to help with automated issue creation.
    • Audit project configuration to see how fields are mapped to different issue types.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • issueTypeId – The ID of the issue type to retrieve metadata for.
    • projectIdOrKey – The ID or key of the project, for example, "PROJ-123" or "10000".
    • (Optional) startAt – The index of the first item to return in a page of results.
    • (Optional) maxResults – The maximum number of items to return per page.
  • Example prompts
    • What fields are required to create a Bug in project PROJ?
    • Show me the field metadata for issue type 10001 in my Jira project.
    • I need to see the available fields for Story tickets in the Development project.
    • List the field definitions and IDs for tasks in project WEB-456.
getJiraProjectIssueTypesMetadata – Retrieves the list of issue types available for a specific project.
  • When to use
    • Find out what types of items can be created in a project, for example, "Task", "Sub-task", "Story", or "Epic".
    • Identify if specific issue types like "Service Request" or "Bug" exist within a project's configuration.
    • Gather the issue type IDs needed for other Jira operations, like retrieving specific field metadata.
    • Understand a project's workflow capability by listing all configured issue types.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • projectIdOrKey – The ID or unique key of the project, for example, "PROJ-123" or "10000".
    • (Optional) startAt – The index of the first item to return in a page of results.
    • (Optional) maxResults – The maximum number of items to return per page.
  • Example prompts
    • What issue types are available in project PROJ?
    • Can you list the different types of tickets I can create in my Jira Marketing project?
    • Show me the issue type IDs for project 10001.
    • I need to know if 'Bug' is a valid issue type in project WEB-456.
getTransitionsForJiraIssue – Retrieves the available transitions (status changes) for a specific Jira issue.
  • When to use
    • Check what status changes are currenty possible for an issue, for example, "In Progress", "Done", or "Reopened".
    • Find a specific transition ID required to move an issue through its workflow.
    • Verify all possible workflow paths for a ticket, including transitions that might currently be hidden or unavailable.
    • Understand the next steps an issue can take to troubleshoot workflow bottlenecks.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • issueIdOrKey – The ID or unique key of the issue, for example, "PROJ-123" or "10000".
    • (Optional) expand – A comma-separated list of additional information to include, for example, "transitions.fields,names".
    • (Optional) transitionId – The ID of a specific transition to check for availability.
    • (Optional) skipRemoteOnlyCondition – Whether to skip conditions that only apply to remote transitions.
    • (Optional) includeUnavailableTransitions – Whether to include transitions that are not currently available for the issue but exist in the workflow.
    • (Optional) sortByOpsBarAndStatus – Whether to sort transitions based on their position in the operations bar and their status.
  • Example prompts
    • What are the available transitions for Jira issue PROJ-123?
    • Can I move story WEB-555 to 'Done'? Show me the workflow status options.
    • Show me all transitions for issue MKT-789, including those that are currently unavailable.
    • Retrieve the status ID needed to move Jira task DEV-101 to 'Code Review'.
getVisibleJiraProjects – Retrieves a list of all Jira projects that you have permission to view.
  • When to use
    • Browse all active projects in a Jira instance to find where you need to create or track work.
    • Search for a specific project by name or keyword when you do not know its exact key.
    • Retrieve a list of projects along with their associated issue types to visualize project capabilities.
    • Audit project access by listing all workspaces visible to your account.
  • Parameters
    • cloudId (Required) – The unique identifier for the Atlassian Cloud instance or site URL.
    • (Optional) searchString – A string used to filter projects by name or key, for example, "Website", "Marketing", or "DEV".
    • (Optional) action – Filters projects based on the user's permission level, for example, "view" or "browse".
    • (Optional) expandIssueTypes – Whether to include the available issue types for each project in the returned list.
    • (Optional) startAt – The index of the first project to return in a paginated list of results.
    • (Optional) maxResults – The maximum number of projects to return in a single page of results.
  • Example prompts
    • List all the Jira projects I can access.
    • Find any projects with 'Mobile' in the title.
    • Show me all visible Jira projects and include their issue types.
    • I need to see a list of my Jira project keys for the Marketing cloud.
jiraRead – Performs general read-only operations in Jira, such as retrieving issue link types.
  • When to use
    • Find the names and types of links available for connecting issues, for example, "Blocks", "Is blocked by", "Duplicate", or "Relates to".
    • Discover configuration details required for operations like createIssueLink.
    • List the system-defined link types to verify which relationship descriptors are supported in your Jira instance.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • action – The specific read operation to perform, for example, "getIssueLinkTypes".
  • Example prompts
    • What are the available issue link types in my Jira project?
    • Show me a list of the allowed ways to link tickets in Jira.
    • I need to see the link configuration types for the Atlassian cloud.
lookupJiraAccountId – Retrieves unique account IDs for Jira users by searching their name or email address.
  • When to use
    • Find the unique identifier for a user to assign them to a ticket, for example, by searching "Jane Smith" or "jane.smith@example.com".
    • Identify the correct account ID when multiple users have similar or identical display names.
    • Resolve user identifiers for tool operations that require an account ID rather than a display name.
    • Verify if a specific team member has an active account in the Jira instance.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • searchString – The query used to find the user, for example, "John Doe", "developer", or "john@example.com".
  • Example prompts
    • Find the Jira account ID for Jane Smith
    • Search for the identifier for user trisha.hanlon@optimizely.com in my Jira site.
    • I need the Jira ID for a user named 'Bob from the product team'.
    • Look up the account ID for the email 'dev-lead@company.com'.

Confluence page and content management

Use these tools to build, update, and collaborate on documentation and pages within Confluence spaces.
createConfluencePage – Creates a new page or blog post in a Confluence space.
  • When to use
    • Generate a new documentation page in a specific space to share project updates, for example, "Project Roadmap" or "Team Meeting Minutes".
    • Create a draft for a blog post within Confluence to communicate company-wide announcements.
    • Organize information by creating nested pages under an existing parent page.
    • Programmatically populate a space with content derived from other tools or research.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • spaceId – The ID of the space where the page should be created.
    • body – The actual content of the page.
    • (Optional) title – The title of the new page or blog post.
    • (Optional) parentId – The ID of the parent page if creating a nested page.
    • (Optional) subtype – The subtype of the content, for example, "page" or "blogpost".
    • (Optional) isPrivate – Whether to make the newly created page private.
    • (Optional) contentFormat – The format of the provided body content, for example, "adf" (Atlassian Document Format) or "markdown".
  • Example prompts
    • Create a new Confluence page in space 12345 titled Project Roadmap with a summary of our Q2 goals.
    • I need to make a markdown page in the Marketing space called Brand Guidelines using the following content.
    • Can you add a sub-page under page ID 98765 titled Meeting Notes in the Engineering space?
    • Generate a blog post in space 55555 announcing the new product launch.
updateConfluencePage – Updates the content, title, or status of an existing Confluence page.
  • When to use
    • Update existing project documentation with new notes or results, for example, adding Q2 performance data to an annual report page.
    • Change the title of a Confluence page to better reflect its current status or contents.
    • Append or replace content on a specific page using research or automated analysis results.
    • Reorganize information by moving a page to a different parent page or space.
    • Archive or change the status of a page to manage content lifecycle within a space.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • pageId – The unique ID of the page to be updated.
    • body – The new content to be applied to the page.
    • (Optional) title – The new title for the page if it needs to be renamed.
    • (Optional) spaceId – The ID of the space where the page is currently located.
    • (Optional) parentId – The ID of the new parent page if moving the page within the hierarchy.
    • (Optional) status – The current status of the page, for example, "current", "archived", or "deleted".
    • (Optional) versionMessage – A description of the changes made in this update for the version history.
    • (Optional) contentFormat – The format of the provided body content, for example, "adf" (Atlassian Document Format) or "markdown".
  • Example prompts
    • Update page ID 12345 in space 54321 with a new project summary using the following list of goals.
    • Change the title of Confluence page 98765 to Q3 Strategic Roadmap and update its content to markdown format.
    • I need to update the meeting notes page with ID 11111 to include the current feedback from the engineering team.
    • Set the status of page ID 22222 to archived and add a version message stating Old project data.
createConfluenceFooterComment – Adds a general comment or a reply to the bottom of a Confluence page.
  • When to use
    • Leave general feedback or a question at the bottom of a Confluence documentation page.
    • Reply to an existing comment thread by associating your message with a parent comment ID.
    • Add a comment to a page and include a reference to a specific attachment, for example, a PDF or an image.
    • Provide a status update or a note on a project page for the rest of the team to see.
  • Parameters
    • cloudId (Required) – The unique identifier for the Atlassian Cloud instance or site URL.
    • body (Required) – The content of the comment in Markdown format.
    • (Optional) pageId – The ID of the page where the comment will be added.
    • (Optional) attachmentId – The ID of an attachment to associate with the comment.
    • (Optional) customContentId – The ID of a custom content item to include.
    • (Optional) parentCommentId – The ID of a parent comment if you are replying to an existing thread.
  • Example prompts
    • Add a footer comment to page 12345 saying the roadmap looks great.
    • Reply to comment ID 99999 on page 10101 by asking for more details on the budget.
    • Leave feedback on the Marketing page with ID 55555 and include attachment ID 44444.
    • Comment on the Engineering wiki page 88888 stating that the architecture diagram needs an update.
createConfluenceInlineComment – Creates an inline comment on specific text within a Confluence page.
  • When to use
    • Highlight a specific sentence or paragraph to ask a clarifying question directly in the context of the content.
    • Provide feedback on a particular phrase, for example, suggesting a wording change or a technical correction.
    • Tag a team member on a specific part of a draft to request an update or approval.
    • Create a reply to an existing inline comment thread to continue a focused discussion.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • body – The content of the comment in Markdown format.
    • (Optional) pageId – The ID of the page where the inline comment is added.
    • (Optional) parentCommentId – The ID of a parent comment if you are replying to an existing thread.
    • (Optional) inlineCommentProperties – The properties defining the text selection, for example, the original text and its position within the page, to highlight it correctly.
  • Example prompts
    • Add an inline comment to page 12345 asking for more data on the highlighted sentence about project goals.
    • Reply to the inline comment 55555 on page 88888 by confirming that the calculation is correct.
    • I need to provide feedback on the second paragraph of the marketing page with ID 44444. Leave a comment suggesting we check the branding.
    • Create a thread on page ID 10101 to explain the API call better for this section of text.

Confluence information and structure

Use these tools to navigate the hierarchy of spaces, pages, and the discussions happening within them.
getConfluencePage – Retrieves full content and metadata for a specific Confluence page.
  • When to use
    • Read the content of a project page to summarize its main points for a team update.
    • Retrieve information from a specific Confluence page ID to answer a research question.
    • Access documentation in a specific format to use the data in other content creation tools, for example, "markdown."
    • Verify the current version or title of a page before making an update.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • pageId – The unique ID of the Confluence page to retrieve, for example, "123456789".
    • (Optional) contentFormat – The format of the returned page body, for example, "adf" (Atlassian Document Format) or "markdown".
  • Example prompts
    • Show me the content of Confluence page 12345.
    • I need to read the meeting notes in the Engineering space from page ID 54321.
    • Retrieve the information on page 98765 and provide it in markdown format.
    • Can you get the details for the Brand Guidelines page with ID 10101?
getConfluencePageDescendants – Retrieves the child pages and descendants of a specific Confluence page.
  • When to use
    • View the hierarchy of pages nested under a specific parent page.
    • Audit a documentation structure to identify all sub-pages in a specific section.
    • Retrieve a list of related pages, for example, all meeting notes under a "Meeting Minutes" parent page.
    • Navigate complex page structures by exploring nested content.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • pageId – The ID of the parent page to retrieve descendants for, for example, "123456789".
    • (Optional) depth – The maximum depth of the hierarchy to traverse, for example, "2" to include children and grandchildren.
    • (Optional) limit – The maximum number of results to return per page.
    • (Optional) cursor – A pagination token used to access the next set of descendants.
  • Example prompts
    • List all the sub-pages under page ID 12345 in the Engineering space.
    • Show me the children of the Project Roadmap page with ID 99999.
    • I need to see all the pages nested under ID 55555, up to two levels deep.
    • Get a list of the descendants for page 10101 in the Marketing space.
getConfluenceSpaces – Retrieves a list of available spaces within a Confluence instance.
  • When to use
    • Browse all the project spaces you have permission to access within Confluence.
    • Find the specific ID or details for a space using its key, for example, "MKT" or "ENG."
    • Filter for specific types of spaces, for example, "global" or "personal" spaces.
    • Identify spaces that are currently archived or assigned specific labels for organization.
    • List a user's favorite spaces to quickly access most-used content.
  • Parameters
    • cloudId (Required) – The unique identifier for the Atlassian Cloud instance or site URL.
    • (Optional) ids – A comma-separated list of space IDs to retrieve.
    • (Optional) keys – A comma-separated list of space keys to retrieve, for example, "MKT,SALE,ENG".
    • (Optional) type – The type of space to filter by, for example, "global" or "personal".
    • (Optional) status – The status of the space to filter by, for example, "current" or "archived".
    • (Optional) start – The starting index of the spaces to return in a paginated list.
    • (Optional) limit – The maximum number of spaces to return per page, with a maximum of 250.
    • (Optional) expand – A comma-separated list of additional properties to include in the response, for example, "description,icon,homepage".
    • (Optional) favourite – Set to true to return only the favorite spaces of the authenticated user.
    • (Optional) favoritedBy – The account ID of a user to filter for spaces they have favorited.
    • (Optional) labels – A comma-separated list of labels to filter the spaces by.
  • Example prompts
    • List all the Confluence spaces available in my cloud instance.
    • Find the details for the Confluence spaces with keys MKT and SALES.
    • Show me all my favorite spaces in Confluence.
    • I need a list of all archived personal spaces.
    • Get the list of Confluence spaces labeled with 'Project-X'.
getPagesInConfluenceSpace – Retrieves a list of pages within a specific Confluence space.
  • When to use
    • View all the pages associated with a specific project or department space.
    • Find a page by its title within a specific space when the page ID is unknown.
    • Filter for pages with a specific status, for example, seeing only "archived" or "draft" pages in a space.
    • List pages in a specific order, for example, alphabetically or by creation date, to organize information.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • spaceId – The ID of the space to retrieve pages from.
    • (Optional) title – A string to filter the results by page title.
    • (Optional) status – The status of the pages to filter by, for example, "current", "archived", "deleted", "draft", or "trashed."
    • (Optional) limit – The maximum number of pages to return in a single page of results, with a maximum of 250.
    • (Optional) cursor – A pagination token used to access the next set of pages.
    • (Optional) sort – The order in which to sort the pages, for example, "title", "-title", "created_date", or "-created_date".
  • Example prompts
    • List all the pages in Confluence space 12345.
    • Show me the current pages in my Marketing space with ID 98765.
    • Find the page titled Brand Guidelines in Confluence space 55555.
    • I need a list of the 10 most recently created pages in space 10101.
getConfluencePageFooterComments – Retrieves the footer comments for a specific Confluence page.
  • When to use
    • Read the feedback and discussion threads located at the bottom of a specific project page.
    • Summarize the consensus or key concerns raised by team members in the comment section.
    • Identify specific comment IDs to reference or reply to using other comment-related tools.
    • Audit the engagement levels of a popular page by listing all of its footer comments.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • pageId – The unique ID of the Confluence page to retrieve comments for.
    • (Optional) limit – The maximum number of comments to return in a single page of results.
    • (Optional) cursor – A pagination token used to access the next set of comments.
    • (Optional) sort – The order in which to sort the comments, for example, "created-date" or "-created-date".
    • (Optional) status – The status of the comments to filter by, for example, "active" or "deleted".
  • Example prompts
    • Show me all the footer comments on Confluence page 12345.
    • I need to see the discussion at the bottom of the Project Roadmap page with ID 99999.
    • List the 10 most recent comments on page 54321 in the Engineering space.
    • Find the active comments on page 10101 to see current team feedback.
getConfluencePageInlineComments – Retrieves the inline comments for a specific Confluence page.
  • When to use
    • Audit feedback on specific sections of a project draft to ensure all stakeholder concerns are addressed.
    • Identify unresolved inline comments (questions or issues) that were left directly on the page text.
    • Summarize targeted discussions happening on specific phrases or paragraphs within a document.
    • Navigate to a particular section of a large page by finding relevant inline comment historical threads.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • pageId – The unique ID of the page to retrieve inline comments for.
    • (Optional) limit – The maximum number of comments to return in a single page of results.
    • (Optional) cursor – A pagination token used to access the next set of results.
    • (Optional) sort – The order in which to sort the comments, for example, "created-date" or "-created-date".
    • (Optional) status – The status of the comments to filter by, for example, "active" or "deleted".
    • (Optional) resolutionStatus – The resolution state of the inline comments, for example, "open" or "resolved".
  • Example prompts
    • Show me the inline comments for Confluence page 12345 in the Engineering space.
    • Are there any unresolved comments on the Q2 Strategy page with ID 99999?
    • I need to see the active feedback on page 54321, sorted by the most recent.
    • Get all the resolved inline comments for the Marketing documentation with ID 10101.
getConfluenceCommentChildren – Retrieves reply (child) comments for a specific parent comment in Confluence.
  • When to use
    • View the full thread of replies to a specific feedback point on a documentation page.
    • Track a conversation or decision process that happened within a comment thread.
    • Audit specific responses to a teammate's question or status update.
    • Go through nested discussions to understand the complete context of a page review.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • commentI – The ID of the parent comment to retrieve replies for.
    • commentType – The type of the parent comment, for example, "footer" or "inline".
    • (Optional) limit – The maximum number of replies to return in a single page of results.
    • (Optional) cursor – A pagination token used to access the next set of replies.
    • (Optional) sort – The order in which to sort the child comments, for example, "created-date" or "-created-date".
  • Example prompts
    • List all the replies to comment ID 12345 on my Confluence page.
    • Show me the child comments for thread ID 99999 to see the team's discussion.
    • I need to see the responses to footer comment 44444 in the Engineering space.
    • Retrieve the 10 most recent replies for the inline comment with ID 55555.

Search and discovery

Use these tools to find specific content across both Jira and Confluence using natural language or structured queries.
search – Searches across both Jira and Confluence using Rovo Search.
  • When to use
    • Find any mention of a specific keyword, for example, "Project Aurora," across all your tickets and documentation.
    • Locate information on a broad topic when you do not know if it is stored in a Jira ticket or a Confluence page.
    • Search your entire Atlassian workspace for historical decisions, project notes, or campaign titles.
    • Retrieve a list of all related content for a project by searching for its name or key.
  • Parameters
    • query – The main search query used to find content across Jira and Confluence, for example, "budget meeting" or "API documentation."
  • Example prompts
    • Search for all documents and tickets related to project Aurora.
    • Find any mention of the budget meeting from last week across Jira and Confluence.
    • I need to find information about our branding guidelines.
    • Search my Atlassian workspace for the keyword Q4 goals.
    • Retrieve any team notes or tasks related to the mobile app launch.
searchJiraIssuesUsingJql – Searches for Jira issues using the Jira Query Language (JQL).
  • When to use
    • Find Jira issues that match complex criteria, for example, "project = 'PROJ' AND status = 'In Progress' AND assignee = currentuser()."
    • Generate a list of high-priority bugs across multiple projects for a weekly report.
    • Identify overdue tasks by searching for tickets where the due date is in the past and the status is not "Done."
    • Perform precise technical searches that standard keyword searches cannot handle.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • jql – The JQL query string used to filter issues, for example, "status = 'To Do' AND priority = 'High'".
    • (Optional) fields – A list of specific fields to include in the search results for each issue.
    • (Optional) maxResults – The maximum number of issues to return per page, for example, "50" or "100."
    • (Optional) nextPageToken – A token used to retrieve the next page of search results.
  • Example prompts
    • Find all the in-progress issues in the Engineering project using JQL.
    • I need to see all the bugs assigned to Jane Smith that are currently high priority.
    • Search for Jira issues where the status is Done and the component is UI/UX.
    • Retrieve all tasks created in the last 7 days from project MKT using a JQL query.
searchConfluenceUsingCql – Searches for Confluence content using the Confluence Query Language (CQL).
  • When to use
    • Perform advanced searches for pages or blog posts with specific labels, for example, "brand-guidelines" or "q3-goals".
    • Find documentation created or updated by a specific user within a set timeframe.
    • Search for pages that belong to specific spaces using complex logic that standard search cannot handle.
    • Identify all blog posts in a space that mention a specific keyword or project name.
  • Parameters
    • cloudId – The unique identifier for the Atlassian Cloud instance or site URL.
    • cql – The CQL query string used to filter content, for example, "title ~ 'meeting' AND type = page".
    • (Optional) cqlcontext – A context used to refine the search results based on specific environments.
    • (Optional) cursor – A pagination token used to access the next set of search results.
    • (Optional) expand – A comma-separated list of properties to expand in the response, for example, "space,version".
    • (Optional) limit – The maximum number of results to return per page, with a limit of 250.
    • (Optional) next – Whether to include a link to the next page of results in the response.
    • (Optional) prev – Whether to include a link to the previous page of results in the response.
  • Example prompts
    • Find all the Confluence pages in the Marketing space created this month that have the label roadmap.
    • Search for blog posts mentioning the new office opening using a CQL query.
    • I need to see all documentation pages updated by Jane Smith in the SALES space.
    • Retrieve a list of pages with the title Branding that were created in the last 7 days.
fetch – Retrieves full information for a Jira issue or Confluence page using its unique Atlassian Resource Identifier (ARI).
  • When to use
    • Quickly retrieve the content of a Jira issue or Confluence page using its specific Atlassian Resource Identifier (ARI).
    • Access granular details of an item found in a previous global search result.
    • Fetch full documentation or ticket data when you have the direct internal identifier from another operation.
    • Streamline data retrieval when working with cross-product references that use the ARI format.
  • Parameters
    • id – The unique Atlassian Resource Identifier (ARI) for the item, for example, "ari:cloud:jira:cloudId:issue/10107" or "ari:cloud:confluence:cloudId:page/123456789".
  • Example prompts
    • Fetch the details for the Atlassian resource ari:cloud:jira:cloudId:issue/10107.
    • Show me the content of the Confluence page with the ID ari:cloud:confluence:cloudId:page/123456789.
    • Get the full information for the ticket referenced at ari:cloud:jira:site-id:issue/55555.
    • Retrieve the documentation for the resource ari:cloud:confluence:site-id:page/98765.

System and account services

Use these tools to identify the current user context and manage connection permissions.
atlassianUserInfo – Retrieves detailed information about the currently authenticated Atlassian user.
  • When to use
    • Identify the account ID of the current user before performing operations like assigning a ticket or filtering a search.
    • Verify which email address or display name is currently authenticated with the Atlassian project.
    • Check user profile metadata, for example, time zone or locale, to ensure correct data formatting.
    • Confirm your permissions and site access by retrieving your own account details.
  • Parameters
    • None
  • Example prompts
    • Show me my Atlassian user information.
    • What is my current Jira account ID?
    • I need to check which email I am logged into Confluence with.
    • Retrieve my user profile details for this Atlassian site.
getAccessibleAtlassianResources – Retrieves the list of Atlassian Cloud IDs (sites) that the user has permission to access.
  • When to use
    • Identify the list of cloud IDs (site URLs) available to use in other Jira or Confluence tool calls.
    • Find the specific site ID for a project, for example, identifying the "Marketing" instance ID.
    • Check which environments are connected before searching across different Atlassian projects.
    • Verify site access when troubleshooting why a specific ticket or page cannot be found.
  • Parameters
    • None
  • Example prompts
    • List all my accessible Atlassian instances.
    • Which Jira and Confluence sites do I have access to?
    • I need to find the cloud ID for my Atlassian workspace.
    • Show me the list of Atlassian resource IDs available for my account.

If you use Opti ID, administrators can turn off generative AI in the Opti ID Admin Center. See Turn generative AI off across Optimizely applications.