GitLab MCP: workItem query fails, workItems works
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- gitlab, graphql, typescript
Research direction
Start by locating the GitLab MCP tools, their built-in guidance or examples, and the handling around gitlab_execute_custom_query; compare the failing workItem field with the working workItems(iid: ...) query. Done means selecting and implementing one agreed improvement—canonical guidance, schema-aware lookup, or a single suggested-field retry—with coverage for the work-item query behavior.
Written by the indexing model from the issue text.
Description
Observed behavior
When querying a GitLab work item via gitlab_execute_custom_query, my first attempt used the field workItem on Project, which failed with:
GraphQL error: Field 'workItem' doesn't exist on type 'Project' (Did you mean `workItems`?)
Retrying with workItems(iid: "...") on Project succeeded and returned the expected work item.
Why this is worth improving
The GitLab GraphQL schema evidently drifted (either workItem was removed/renamed, or it never existed on Project and only workItems did). The agent-side pattern is:
- First call fails with a schema error.
- Agent reads the "Did you mean" hint from the error and adjusts.
- Second call succeeds.
This works, but it wastes a round-trip on every session that touches work items, and it depends on the agent noticing the hint. A more robust experience would be one of:
- Auto-retry once when the error message contains a
Did you meansuggestion, substituting the suggested field. - A schema-aware helper (e.g.,
gitlab_get_type_fieldsresults cached and surfaced in the tool description) so the agent picks the right field on the first try. - Update any built-in guidance/examples in the GitLab MCP tools to reference
workItems(iid: ...) { nodes { ... } }as the canonical way to fetch a single work item by IID on a Project.
Impact: minor per-call latency + agent context spent on the schema hint. Not blocking, but repeatable across sessions.
Metadata
| Field | Value |
|---|---|
| CLI Version | 0.8.10 |
| Platform | darwin |
| Architecture | arm64 |
| OS Release | 25.5.0 |
| Category | improvement |
| Working Directory | feature-1173-parallel-ci-databases |
| Session ID | ses_0c9a0177effeYuBnIpoLd52aQ1 |
- Dominant language
- TypeScript
- Stars
- 813
- Forks
- 134
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 63
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AltimateAI/altimate-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
AltimateAI/altimate-code#1323 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AltimateAI/altimate-code#1288 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AltimateAI/altimate-code#1285 ·
-
privacy: Altimate Base consent dialog no longer discloses persistent per-installation identifier Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
AltimateAI/altimate-code#1284 ·
-
Difficulty 2/5 Under an hour Newbie friendliness 72/100
AltimateAI/altimate-code#1283 ·
All issues in AltimateAI/altimate-code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·