MCP Jira search can silently return incomplete results with no valid next-page cursor

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • Component/s: AI - MCP - Tools
    • None
    • 1
    • Severity 3 - Minor

      Issue Summary

      searchJiraIssuesUsingJql can return incomplete Jira search results through MCP clients when a query matches more than five issues.

      The response may contain only the first five issues while reporting that no next page is available. This prevents the client from retrieving the remaining matching issues and can result in incomplete AI responses or analysis.

      The underlying Jira data is not modified or lost. The issue affects the MCP search response returned to the client.

      Steps to Reproduce

      1. Use an MCP client and call searchJiraIssuesUsingJql with a JQL query that returns more than five issues.
      2. Compare the total number of matching issues from Jira, or from searchResultMode: "count", with the issues returned in structuredContent.issues.nodes.

      Expected Results

      The MCP response should return all issues included in the Jira server response page.
      If additional results exist beyond the current response page, the response should provide:

      {   "hasNextPage": true,   "endCursor": "<usable cursor>" }

      The client should be able to retrieve all matching Jira issues through standard pagination.

      Actual Results

      The MCP response can return only five issues in:

      structuredContent.issues.nodes 

      while also returning pagination metadata similar to:

      {
        "remainingCount": 16,
        "pageInfo": {
          "hasNextPage": false,
          "endCursor": null
        }
      } 

      This is contradictory because the response indicates that additional matching issues exist, but does not provide a way to retrieve them.

      A client that follows hasNextPage: false stops after the first five issues, resulting in incomplete search results.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Vanessa Fei Wang
              Reporter:
              Leo.Soronio
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: