Problem Definition

The getJiraIssue MCP tool returns comments embedded in the full issue payload, in ascending order, with no pagination.

For issues with long comment threads (20+ comments with rich content), the MCP response hits a size limit and is silently truncated, dropping the newest comments - which are typically the most important.

Customers need full comment history to run analysis on the history of longest-running blocked tickets - understanding response times, escalation patterns, blocker durations, and PM engagement across the project.

Silent truncation makes this analysis unreliable and forces manual workarounds that defeat the purpose of the MCP integration.

Suggested Solution

• Dedicated Comment Tool:  A dedicated getJiraIssueComments tool - separate from getJiraIssue, with its own pagination (cursor-based), configurable sort order (ascending/descending), and a reasonable page size. This mirrors how the Jira REST API already supports /rest/api/3/issue/ {issueIdOrKey} /comment with startAt, maxResults, and orderBy.
• Increased Limits:  Alternatively, increase the response size limit for getJiraIssue or allow a maxComments parameter so consumers can control how much comment data is returned.
• Default Sort Order: Return comments in descending order (newest first) as an option - for many use cases, recent comments matter most, and if truncation must happen, losing old comments is far less damaging.

Workaround

n/a