Skip to main content
Glama
PhialsBasement

GitHub MCP Server Plus

list_issues

Retrieve and filter issues from GitHub repositories by state, labels, date, and sorting criteria to manage project tasks effectively.

Instructions

List issues in a GitHub repository with filtering options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
repoYes
directionNo
labelsNo
pageNo
per_pageNo
sinceNo
sortNo
stateNo

Implementation Reference

  • Core handler function that builds the GitHub API URL with query parameters and fetches the list of issues.
    export async function listIssues(
      owner: string,
      repo: string,
      options: Omit<z.infer<typeof ListIssuesOptionsSchema>, "owner" | "repo">
    ) {
      const urlParams: Record<string, string | undefined> = {
        direction: options.direction,
        labels: options.labels?.join(","),
        page: options.page?.toString(),
        per_page: options.per_page?.toString(),
        since: options.since,
        sort: options.sort,
        state: options.state
      };
    
      return githubRequest(
        buildUrl(`https://api.github.com/repos/${owner}/${repo}/issues`, urlParams)
      );
    }
  • Zod schema defining the input options for the list_issues tool, including owner, repo, and various filters.
    export const ListIssuesOptionsSchema = z.object({
      owner: z.string(),
      repo: z.string(),
      direction: z.enum(["asc", "desc"]).optional(),
      labels: z.array(z.string()).optional(),
      page: z.number().optional(),
      per_page: z.number().optional(),
      since: z.string().optional(),
      sort: z.enum(["created", "updated", "comments"]).optional(),
      state: z.enum(["open", "closed", "all"]).optional(),
    });
  • index.ts:123-127 (registration)
    Tool registration in the listTools response, specifying name, description, and input schema.
    {
      name: "list_issues",
      description: "List issues in a GitHub repository with filtering options",
      inputSchema: zodToJsonSchema(issues.ListIssuesOptionsSchema)
    },
  • Dispatch handler in the main CallToolRequestSchema switch that parses arguments and delegates to the issues.listIssues function.
    case "list_issues": {
      const args = issues.ListIssuesOptionsSchema.parse(request.params.arguments);
      const { owner, repo, ...options } = args;
      const result = await issues.listIssues(owner, repo, options);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic action. It doesn't mention whether this is a read-only operation, if it requires authentication, how pagination works (despite 'page' and 'per_page' parameters), rate limits, or what the output format looks like. This leaves critical behavioral traits undocumented.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the core purpose ('List issues in a GitHub repository') and adds essential context ('with filtering options') without any wasted words. It's appropriately sized for the tool's complexity.

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

Completeness2/5

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

Given the tool's complexity (9 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return values, pagination behavior, authentication requirements, or how to interpret parameters like 'direction' or 'sort'. For a listing tool with rich filtering options, more context is needed to use it effectively.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but only vaguely mentions 'filtering options' without explaining any of the 9 parameters. It doesn't clarify what 'owner', 'repo', or other parameters mean, their formats (e.g., 'since' as timestamp), or how filtering works with arrays like 'labels'. The description adds minimal value beyond the bare schema.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('issues in a GitHub repository') with scope ('with filtering options'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'search_issues' or 'get_issue', which handle similar resources but with different approaches.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'search_issues' or 'get_issue'. It mentions filtering options but doesn't specify scenarios where this listing approach is preferred over searching or retrieving individual issues, leaving the agent without usage context.

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/PhialsBasement/mcp-github-server-plus'

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