René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"infra: expose review thread node ID in get_review_comments response (follow-up to #1768)","articleBody":"## Background\n\nAfter #1768 shipped, `resolve_review_thread` is available as an MCP tool. However, the companion read path — retrieving a review thread's GraphQL node ID so it can be passed to `resolve_review_thread` — is still missing from the response schema.\n\nWhen an AI agent is addressing PR review feedback, the typical flow is:\n\n1. Read review comments with `pull_request_read method=get_review_comments`.\n2. Reply to the comment with `add_reply_to_pull_request_comment`.\n3. Resolve the thread with `resolve_review_thread`.\n\nStep 3 requires the thread's node ID (e.g. `PRRT_kwDO...`), but step 1's response does not expose it.\n\n## Problem\n\n`pull_request_read method=get_review_comments` returns each `review_threads[]` object with these fields only:\n\n```json\n{\n  \"is_resolved\": false,\n  \"is_outdated\": false,\n  \"is_collapsed\": false,\n  \"comments\": [...],\n  \"total_count\": N\n}\n```\n\nThere is **no `id` / `node_id` field on the thread object**, so there is no way to obtain the value `resolve_review_thread` requires.\n\nAuxiliary paths are also blocked:\n\n- `add_reply_to_pull_request_comment` returns the *comment*'s node ID (`PRRC_...`), which is distinct from the thread's node ID.\n- `pageInfo.startCursor` / `endCursor` are pagination cursors, not thread IDs.\n- Within an MCP-only session there is no `gh` CLI or direct GraphQL escape hatch.\n\nNote: issue #1768 stated that \"the thread IDs are already returned by `get_review_comments` in the `ID` field\". That does not appear to match the current shipped response schema — the `ID` field is absent on the thread object as of 2026-04-15.\n\n## Reproduction\n\nOn any PR with multiple unresolved review threads, calling `pull_request_read method=get_review_comments` returns no field usable as the `thread_id` argument of `resolve_review_thread`. This was observed while addressing Copilot PR reviewer feedback on a PR with 5 unresolved threads — the workflow had to fall back to manual `gh api graphql` calls outside MCP to complete step 3.\n\nMinimal repro outside MCP — compare the current MCP response shape to this GraphQL query, which does expose the thread `id`:\n\n```graphql\n{\n  repository(owner: \"\u003cowner\u003e\", name: \"\u003crepo\u003e\") {\n    pullRequest(number: \u003cn\u003e) {\n      reviewThreads(first: 50) {\n        nodes { id isResolved isOutdated }\n      }\n    }\n  }\n}\n```\n\nThe MCP response should surface the same `id` field on each thread.\n\n## Proposal\n\nEither:\n\n1. **Extend the `get_review_comments` response schema** — include `PullRequestReviewThread.id` (GraphQL node ID) as `id` or `node_id` on each thread object.\n2. **Add a dedicated method** — `pull_request_read method=get_review_threads` that returns a thin list of threads with their node IDs (and the existing `is_resolved` / `is_outdated` / `is_collapsed` flags).\n\nOption 1 is likely a single-field addition: the underlying GraphQL query almost certainly already selects the thread object (since `isResolved`/`isOutdated`/`isCollapsed` are exposed), so adding `id` to the same selection set should be a minimal change.\n\n## Current workaround\n\nFor MCP-only sessions, `resolve_review_thread` is effectively unreachable — users must drop out of MCP and click \"Resolve conversation\" in the GitHub web UI (or run `gh api graphql` outside the session). This defeats the purpose of shipping the tool in #1768.\n\n## References\n\n- #1768 — original request that added `resolve_review_thread`\n- #1086 — `is_resolved` exposure on comments\n- MCP tool list snapshot date: 2026-04-15","author":{"url":"https://github.com/kogangdon","@type":"Person","name":"kogangdon"},"datePublished":"2026-04-15T03:32:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/2331/github-mcp-server/issues/2331"}