You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Return COMPLETE data or state what's missing (e.g. pages skipped).
100
-
101
-
list_project_items query rules:
102
-
Query string - For advanced filtering of project items using GitHub's project filtering syntax:
103
-
104
-
MUST reflect user intent; strongly prefer explicit content type if narrowed:
105
-
- "open issues" → state:open is:issue
106
-
- "merged PRs" → state:merged is:pr
107
-
- "items updated this week" → updated:>@today-7d (omit type only if mixed desired)
108
-
- "list all P1 priority items" → priority:p1 (omit state if user wants all, omit type if user specifies "items")
109
-
- "list all open P2 issues" → is:issue state:open priority:p2 (include state if user wants open or closed, include type if user specifies "issues" or "PRs")
110
-
- "all open issues I'm working on" → is:issue state:open assignee:@me
111
-
112
-
Query Construction Heuristics:
113
-
a. Extract type nouns: issues → is:issue | PRs, Pulls, or Pull Requests → is:pr | tasks/tickets → is:issue (ask if ambiguity)
114
-
b. Map temporal phrases: "this week" → updated:>@today-7d
115
-
c. Map negations: "excluding wontfix" → -label:wontfix
116
-
d. Map priority adjectives: "high/sev1/p1" → priority:high OR priority:p1 (choose based on field presence)
117
-
e. When filtering by label, always use wildcard matching to account for cross-repository differences or emojis: (e.g. "bug 🐛" → label:*bug*)
118
-
f. When filtering by milestone, always use wildcard matching to account for cross-repository differences: (e.g. "v1.0" → milestone:*v1.0*)
119
-
120
-
Syntax Essentials (items):
121
-
AND: space-separated. (label:bug priority:high).
122
-
OR: comma inside one qualifier (label:bug,critical).
123
-
NOT: leading '-' (-label:wontfix).
124
-
Hyphenate multi-word field names. (team-name:"Backend Team", story-points:>5).
- First inspect item's content object for info, e.g. title, assignees, labels
1224
-
- If additional detail is needed, and relevant fields are present from list_project_fields, include their IDs in list_project_items and request with list_project_items again.
1225
-
- If more detail needed, use separate issue/PR tools`),
1226
-
},
1227
-
{
1228
-
Role:"assistant",
1229
-
Content:mcp.NewTextContent(`Query patterns for list_project_items:
1230
-
1231
-
Common scenarios:
1232
-
- Blocked issues: is:issue (label:blocked OR status:"Blocked")