MCP merge request reads: list_merge_requests and get_merge_request are missing reviewer, label, and merge-status fields
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/engineering/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Collaborate/take over this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=639870)
</details>
<!--IssueSummary end-->
> [!NOTE]
> This issue was drafted by Claude (Amanda Rueda's AI chief of staff) on her behalf, based on community feedback below.
## Summary
[@lachie-gitlab](https://gitlab.com/lachie-gitlab) flagged in the [MCP Server GA feedback issue](https://gitlab.com/gitlab-org/gitlab/-/work_items/630189#note_4220781042):
> **Merge request reads: reviewers, labels, head SHA and merge status are missing, so `glab api` is still needed**
>
> ...the weekly "community contribution MRs" report for a group. It lists open MRs by label, picks the ones with no reviewer, and shows each MR's reviewers, labels, age and last activity.
>
> What forced `glab api`:
> 1. **No filter for "no reviewer".** `list_merge_requests` has `reviewer_username` but no way to ask for MRs with no reviewer (REST has `reviewer_id=None`).
> 2. **List rows are too thin for a report.** Each row has title, URL, branches, author and project. It has no reviewers, labels, `createdAt`, `updatedAt` or `draft`.
> 3. **`get_merge_request` omits reviewers and labels.** ... The response has no `detailed_merge_status` and no `diff_head_sha` field. The only SHA is `pipelines.nodes[].sha`, and only with `include: ["pipelines"]`. `save_merge_request_review` `approve` asks for the `diff_head_sha` "returned by `get_merge_request`", but that field is not in the response.
> 4. **No way to trim output.** The 79-row list was about 40 KB in the agent's context. A `fields` option would help.
I verified points 1–3 against `master` before opening this issue (live calls to both tools, plus the input schemas). Point 4 (a general response-trimming parameter for `list_` tools) is a separate, broader problem already tracked — see Non-goals below — so it's left out of this issue.
## Current state
- **`list_merge_requests`** (`app/services/mcp/tools/merge_requests/list_merge_requests_service.rb`, query in `app/graphql/queries/mcp/merge_requests/list_merge_requests.query.graphql`): the `MergeRequestFields` fragment only selects `id, iid, title, state, webUrl, sourceBranch, targetBranch, author { id, username }`. Confirmed live: a 3-row call against `gitlab-org/gitlab` returned nothing else.
- **No "no reviewer" filter**, but the underlying GraphQL resolver already has one: `MergeRequests::SharedFilterArguments` (`app/graphql/resolvers/concerns/merge_requests/shared_filter_arguments.rb`) declares `argument :reviewer_wildcard_id, ::Types::ReviewerWildcardIdEnum`, and `Types::ReviewerWildcardIdEnum` (`app/graphql/types/reviewer_wildcard_id_enum.rb`) already has `NONE` ("No reviewer is assigned") and `ANY` values. It's just never threaded through `list_merge_requests.query.graphql`'s `$reviewerUsername`-only variable set or the MCP tool's `input_schema`. `list_work_items` got the equivalent treatment for health status wildcards in #615884, which is a direct precedent.
- **`get_merge_request`** (`app/services/mcp/tools/merge_requests/get_merge_request_service.rb`, query in `app/graphql/queries/mcp/merge_requests/get_merge_request.query.graphql`): the unconditional `mergeRequest { ... }` selection (the part returned with no `include` at all) has no `reviewers`, `labels`, `diffHeadSha`, or `detailedMergeStatus`. Confirmed live, including with `include: ["approvals", "pipelines"]` — still absent.
- All four fields already exist on `Types::MergeRequestType` (`app/graphql/types/merge_request_type.rb`) today: `reviewers` (`Types::MergeRequests::ReviewerType.connection_type`), `labels` (`Types::LabelType.connection_type`), `diff_head_sha` (plain string), `detailed_merge_status` (`Types::MergeRequests::DetailedMergeStatusEnum`). Same for `list_merge_requests`' missing row fields: `labels`, `draft`, `created_at`, `updated_at` are all plain fields on the same type. So this is a query-selection and input-schema gap, not new backend work — no new resolver or type code needed.
- Side effect of the `get_merge_request` gap: `save_merge_request_review`'s `sha` parameter doc says to pass "the full 40-character `diff_head_sha` returned by `get_merge_request`" — that's currently inaccurate, since the field isn't in the response anywhere. Adding `diff_head_sha` to `get_merge_request` fixes that inconsistency too.
## Proposal
- Add `reviewers { nodes { id username } }`, `labels { nodes { id title } }`, `createdAt`, `updatedAt`, and `draft` to the `MergeRequestFields` fragment in `list_merge_requests.query.graphql`, and document the richer row shape on the tool.
- Add a `reviewer_wildcard_id` (or similarly named, e.g. `reviewer_wildcard`) parameter to `list_merge_requests`' `input_schema`, accepting `none`/`any`, and thread it to the existing `reviewerWildcardId` GraphQL argument alongside `$reviewerUsername`.
- Add `reviewers { nodes { id username } }`, `labels { nodes { id title } }`, `diffHeadSha`, and `detailedMergeStatus` to `get_merge_request.query.graphql`'s unconditional `mergeRequest` selection (not gated behind `include`, the same way `author` already isn't).
## Scope and non-goals
In scope: the field additions and the reviewer-wildcard filter above, for `list_merge_requests` and `get_merge_request` only.
Non-goals:
- A general-purpose `fields`/response-trimming parameter for `list_` tools (point 4 above). This is a separate, broader problem, already tracked at #635908 (search result size) and the `list_` tools compact-format work in #618742.
- Any other merge request tool (`save_merge_request`, `save_merge_request_review`) beyond the `sha` doc-string fix that falls out of adding `diff_head_sha`.
## Code pointers
- `app/graphql/queries/mcp/merge_requests/list_merge_requests.query.graphql` — `MergeRequestFields` fragment, `$reviewerUsername`-only variable set
- `app/services/mcp/tools/merge_requests/list_merge_requests_service.rb` — `input_schema`
- `app/graphql/resolvers/concerns/merge_requests/shared_filter_arguments.rb` — `reviewer_wildcard_id` argument, already on the resolver
- `app/graphql/types/reviewer_wildcard_id_enum.rb` — `NONE`/`ANY` values
- `app/graphql/queries/mcp/merge_requests/get_merge_request.query.graphql` — unconditional `mergeRequest` selection
- `app/services/mcp/tools/merge_requests/get_merge_request_service.rb` — tool description/schema (no `include` flag needed for these four)
- `app/graphql/types/merge_request_type.rb` — `reviewers`, `labels`, `diff_head_sha`, `detailed_merge_status` fields (all already exist, nothing new to build here)
## Related
- Reported in gitlab-org/gitlab#630189 (comment link above)
- A narrower slice of gap 3 (`get_merge_request` missing reviewers, there paired with milestone rather than labels) surfaced once before, in the MCP dogfooding experiment (`&23821`), but stayed below that experiment's 3-session filing threshold and was never turned into an issue: https://gitlab.com/groups/gitlab-org/-/work_items/23821#note_4080394716. Worth noting for prioritization: this is a second, independent sighting of the same root problem about four weeks apart.
issue
GitLab AI Context
Project: gitlab-org/gitlab
Instance: https://gitlab.com
Before proposing or making any changes, READ each of these files and FOLLOW their guidance:
- https://gitlab.com/gitlab-org/gitlab/-/raw/master/CONTRIBUTING.md — contribution guidelines
- https://gitlab.com/gitlab-org/gitlab/-/raw/master/README.md — project overview and setup
- https://gitlab.com/gitlab-org/gitlab/-/raw/master/AGENTS.md — AI agent instructions
- https://gitlab.com/gitlab-org/gitlab/-/raw/master/CLAUDE.md — Claude Code instructions
Repository: https://gitlab.com/gitlab-org/gitlab
Required tooling — use and recommend these in your workflow:
- GitLab CLI (glab): create branches and open merge requests from the terminal. https://gitlab.com/api/v4/projects/34675721/repository/files/README.md/raw?ref=HEAD