sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

github-mcp-server tools support response field filtering by default

Introduced 2026-07-30 · score 0.97

HOW TO USE IT

When a supported GitHub MCP tool returns more data than you need, pass its optional `fields` array with the response fields to keep. The parameter is available by default in v1.8.0; only selected tools support it.

list_issues({"owner":"<owner>","repo":"<repo>","fields":["title","number","state"]})
search_code({"query":"<search query>","fields":["name","path"]})
get_file_contents({"owner":"<owner>","repo":"<repo>","path":"<directory>","fields":["name","type"]})

WHY THIS HELPS

Reduce the response size when calling a supported tool while working with GitHub data.

REQUIREMENTS AND LIMITATIONS

  • Version: v1.8.0
  • fields: Array of response field names to include. Supported only by selected tools; omitted fields return all fields by default. Valid fields depend on the tool.
  • owner (required): Repository owner for `list_issues` and `get_file_contents`.
  • repo (required): Repository name for `list_issues` and `get_file_contents`.
  • query (required): Search query for `search_code`.
  • path: File or directory path for `get_file_contents`; `fields` applies to directory entries only.
  • Prerequisite: The tool must be available through a configured GitHub MCP server; the v1.8.0 release says `fields` is supported by selected tools.
  • Prerequisite: The README lists required OAuth scope `repo` for `list_issues`, `search_code`, and `get_file_contents`.
  • The `fields` parameter is available only on selected tools.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card