Describe the bug
When a comment in a GitHub Issue is marked as spam, it will be collapsed in the human view, but on the MCP side, the agent has no idea that it's marked as spam. It just treats it like a regular comment.
Affected version
Please run docker run -i --rm ghcr.io/github/github-mcp-server ./github-mcp-server --version and paste the output below
GitHub MCP Server bundled with Copilot SDK 1.0.15-unstable.35393089353.gfc44743, running through runtime 1.0.85-unstable.r35379093703.g3514c9a. Running via Agent Host on VS Code (VS Code version 1.139.0-insider commit 92e4d1b6124d662396f19665be324cbb83eabe83).
Steps to reproduce the behavior
- Find a GitHub Issue with a comment in it that is marked as spam
- Ask the AI to read the GitHub Issue
- It will read the comment that was marked as spam as if it were any other comment. It doesn't know that the comment is marked as spam, even when you directly ask it.
Expected vs actual behavior
I expect the agent to know when a comment is marked as spam. Either that, or not have access to it at all.
Logs
N/A
Describe the bug
When a comment in a GitHub Issue is marked as spam, it will be collapsed in the human view, but on the MCP side, the agent has no idea that it's marked as spam. It just treats it like a regular comment.
Affected version
Please run
docker run -i --rm ghcr.io/github/github-mcp-server ./github-mcp-server --versionand paste the output belowGitHub MCP Server bundled with Copilot SDK 1.0.15-unstable.35393089353.gfc44743, running through runtime 1.0.85-unstable.r35379093703.g3514c9a. Running via Agent Host on VS Code (VS Code version 1.139.0-insider commit 92e4d1b6124d662396f19665be324cbb83eabe83).
Steps to reproduce the behavior
Expected vs actual behavior
I expect the agent to know when a comment is marked as spam. Either that, or not have access to it at all.
Logs
N/A