Skip to main content
Glama
ddukbg

GitHub Enterprise MCP Server

list-issues

Retrieve GitHub issues from a repository with filters for state, sorting, and pagination to manage project tracking and collaboration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (user or organization)
repoYesRepository name
stateNoIssue state filteropen
sortNoSort criteriacreated
directionNoSort directiondesc
pageNoPage number
per_pageNoItems per page

Implementation Reference

  • Registers the MCP tool 'list-issues' with Zod input schema and handler that calls the IssuesAPI.listIssues function, formats the response, and returns it in MCP format.
      "list-issues",
      {
        owner: z.string().describe(i18n.t('issues', 'param_owner')),
        repo: z.string().describe(i18n.t('issues', 'param_repo')),
        state: z.enum(['open', 'closed', 'all']).default('open').describe(i18n.t('issues', 'param_state')),
        sort: z.enum(['created', 'updated', 'comments']).default('created').describe(i18n.t('issues', 'param_sort')),
        direction: z.enum(['asc', 'desc']).default('desc').describe(i18n.t('issues', 'param_direction')),
        page: z.number().default(1).describe(i18n.t('common', 'param_page')),
        per_page: z.number().default(30).describe(i18n.t('common', 'param_per_page'))
      },
      async ({ owner, repo, state, sort, direction, page, per_page }) => {
        try {
          // Parameter validation
          if (!owner || typeof owner !== 'string' || owner.trim() === '') {
            return {
              content: [
                {
                  type: "text",
                  text: i18n.t('common', 'error_required', { field: i18n.t('issues', 'param_owner') })
                }
              ],
              isError: true
            };
          }
    
          if (!repo || typeof repo !== 'string' || repo.trim() === '') {
            return {
              content: [
                {
                  type: "text",
                  text: i18n.t('common', 'error_required', { field: i18n.t('issues', 'param_repo') })
                }
              ],
              isError: true
            };
          }
    
          const issues = await context.issues.listIssues(context.client, {
            owner,
            repo,
            state,
            sort,
            direction,
            page,
            per_page
          });
    
          // No issues found
          if (!issues || issues.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: i18n.t('issues', 'issue_not_found', { owner, repo, state })
                }
              ]
            };
          }
    
          // Format issues info for better readability
          const formattedIssues = issues.map(issue => ({
            number: issue.number,
            title: issue.title,
            state: issue.state,
            user: issue.user.login,
            created_at: issue.created_at,
            updated_at: issue.updated_at,
            body: issue.body ? (issue.body.length > 100 ? issue.body.substring(0, 100) + '...' : issue.body) : '',
            comments: issue.comments,
            labels: issue.labels.map((label: any) => label.name),
            assignees: issue.assignees?.map((assignee: any) => assignee.login) || []
          }));
    
          return {
            content: [
              {
                type: "text",
                text: i18n.t('issues', 'issue_list_title', { owner, repo, count: issues.length }) + `\n\n${JSON.stringify(formattedIssues, null, 2)}`
              }
            ]
          };
        } catch (error: any) {
          console.error(i18n.t('common', 'error_generic', { message: error.message }));
          return {
            content: [
              {
                type: "text",
                text: i18n.t('common', 'error_generic', { message: error.message })
              }
            ],
            isError: true
          };
        }
      }
    );
  • Core handler function that executes the GitHub API request to list issues for a given repository, constructing the query parameters dynamically.
    export async function listIssues(
      client: GitHubClient,
      params: ListIssuesParams
    ): Promise<Issue[]> {
      const { owner, repo, ...rest } = params;
      const queryParams = new URLSearchParams();
      
      // Add additional parameters
      Object.entries(rest).forEach(([key, value]) => {
        if (value !== undefined) {
          queryParams.append(key, String(value));
        }
      });
      
      const queryString = queryParams.toString() ? `?${queryParams.toString()}` : '';
      return client.get<Issue[]>(`/repos/${owner}/${repo}/issues${queryString}`);
    }
  • TypeScript interface defining the input parameters for the listIssues function, matching the Zod schema used in tool registration.
    export interface ListIssuesParams {
      owner: string;
      repo: string;
      state?: 'open' | 'closed' | 'all';
      sort?: 'created' | 'updated' | 'comments';
      direction?: 'asc' | 'desc';
      since?: string;
      page?: number;
      per_page?: number;
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ddukbg/github-enterprise-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server