list_discussions and get_discussion should include upvoteCount

Open Beginner friendly
#2,661 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
go, graphql
Domain
api

Research direction

Locate the implementations of the list_discussions and get_discussion tools and inspect the GraphQL queries they use. Add upvoteCount to both returned results, then verify that the GraphQL responses and tool JSON include the field without requiring new permissions.

Written by the indexing model from the issue text.

Description

enhancement

list_discussions and get_discussion should include upvoteCount

Summary

The list_discussions and get_discussion tools currently return metadata like title, created_at, updated_at, and comments.totalCount, but omit upvoteCount. This field is available on the Discussion type in GitHub's GraphQL API and is the primary signal for gauging community demand on a feature request.

Use case

When using these tools to triage feature request discussions (e.g. scanning a repo's FR backlog as a PM), vote count is a critical prioritisation input. Without it, the only available proxy for demand is comment count or last-activity date — both of which are noisy signals (a thread with 2 comments and 400 upvotes looks identical to one with 2 comments and 3 upvotes).

Proposed change

Add upvoteCount to the GraphQL query used by both list_discussions and get_discussion. The field is already on the Discussion type:

discussion(number: 48) {
  upvoteCount   # add this
  title
  createdAt
  updatedAt
  comments { totalCount }
}

No new permissions are required — upvoteCount is accessible with the existing read:discussion scope.

Expected output
{
  "number": 48,
  "title": "Open letter for improving Home Assistant's Authentication system",
  "upvoteCount": 412,
  "created_at": "2025-06-22T10:18:35Z",
  "updated_at": "2026-05-01T09:12:00Z"
}
Dominant language
Go
Stars
33.1k
Forks
5k
Avg merge
2d 15h
Merged PRs (30d)
27

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/github-mcp-server

All issues in github/github-mcp-server

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.