René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"list_pull_request_reviews silently truncates results to first page (~30 items) with no pagination support","articleBody":"## Describe the bug\n\nThe `list_pull_request_reviews` tool (maps to `GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews`) only returns the first page of results (~30 reviews) and provides no way to fetch subsequent pages. There is no `page`, `per_page`, or cursor parameter exposed, and there is no indication in the response that results were truncated.\n\n**Impact:** On PRs with many review passes (e.g., iterative CI-driven review loops), the most recent reviews are silently absent. The caller receives a valid-looking response with no error or truncation signal, making it impossible to distinguish \"no review yet\" from \"review exists but is on page 2+\".\n\nThis is a silent data-loss bug — the tool returns success with a subset of results and no indication that more exist.\n\n## Steps to reproduce\n\n1. Create a PR that accumulates more than 30 review events (a mix of author reply reviews and bot reviews both count toward the limit).\n2. Call the MCP `list_pull_request_reviews` tool on that PR.\n3. Observe: response stops at ~review #30 regardless of total review count. The most recent reviews are absent.\n\n## Workaround\n\nThe underlying REST API supports pagination. The following `gh` CLI command fetches all pages correctly:\n\n```bash\ngh api repos/\u003cowner\u003e/\u003crepo\u003e/pulls/\u003cnumber\u003e/reviews --paginate \\\n  --jq '.[] | {id, user: .user.login, submitted_at, body: .body[0:120]}' \\\n  | tail -1\n```\n\n## Expected behavior\n\nOne of:\n- **(a)** Expose `page` / `per_page` parameters so callers can paginate.\n- **(b)** Internally paginate and return all results in a single call.\n- **(c)** Include a `has_more: true` field or `total_count` in the response so callers know the result is partial.\n\nOption (b) is preferred for agentic use cases — agents have no retry/pagination loop and silently act on incomplete data.\n\n## Additional context\n\n- This same truncation likely affects other list endpoints (e.g., `list_issues`, `list_pull_requests`) that map to paginated GitHub REST APIs.\n- Confirmed against `github/github-mcp-server` via VS Code Copilot agent session; the MCP tool returned 30 reviews while `gh api --paginate` returned the full set including the most recent review on the current head SHA.","author":{"url":"https://github.com/nishantnaagnihotri","@type":"Person","name":"nishantnaagnihotri"},"datePublished":"2026-04-20T05:25:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2347/github-mcp-server/issues/2347"}