Repository navigation
Query must include 'is:issue' or 'is:pull-request' on search_issues #462
Description
Activity
- changed the title
[-]search_issues[/-][+]Query must include 'is:issue' or 'is:pull-request' on `search_issues`[/+]on Jun 1, 2025 I am actually planning on splitting the tool in two, and doing it as separate tools.
I have an open PR for doing it for search users to split orgs and users. I'm not 100% about merging it, but the same PR to split issues and PRs search and put them into the appropriate toolsets would definitely get merged.
We need that in feel.
@SamMorrowDrums out of curiousity, are you still willing to split issues from PRs?
From the semantical perspective, I believe that splitting would be less error-prone for the LLM as it has to choose between two different functions.@raffaeler yes - in the latest pr we split the search query into two and gave better tool description to avoid the confusion.
Reacted by Raf (Raffaele Rialdi)Thanks @JoannaaKL I didn´t see that, great job!
Reacted by Sam Morrow and JoannaaKLIt will be in our next release, and is on main already.
Reacted by Raf (Raffaele Rialdi) and JoannaaKL
Describe the bug
Every time the
search_issuesin invoked I get this "error" (Query must include 'is:issue' or 'is:pull-request').Anyway, the request goes on and the answer contains the results.
A clear and concise description of what the bug is.
Affected version
Steps to reproduce the behavior
I can see the error just because I log all the traffic, otherwise standard MCP clients normally don't bother about errors that are not blocking.
The query is "AssemblyLoadContext" on the
dotnet/runtimerepository.While the repo may be not the best value passed to the mcp server (it's the LLM creating it), the error does not depend on it.
Expected vs actual behavior
The error should not occur even if it is not blocking.