Skip to main content
Glama

github_checks_list_for_suite

Retrieve check runs for a specified check suite, with filters for name, status, and pagination to manage results.

Instructions

List check runs in a check suite

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesowner
repoYesrepo
check_suite_idYescheck_suite_id
check_nameNoReturns check runs with the specified `name`.
statusNoReturns check runs with the specified `status`.
filterNoFilters check runs by their `completed_at` timestamp. `latest` returns the most recent check runs.
per_pageNoThe number of results per page (max 100). For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
pageNoThe page number of the results to fetch. For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."

Implementation Reference

  • Handler for github_checks_list_for_suite: makes a GET request to the GitHub API to list check runs in a check suite, with optional query parameters for check_name, status, filter, per_page, and page.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/repos/${args.owner}/${args.repo}/check-suites/${args.check_suite_id}/check-runs`, undefined, { check_name: args.check_name, status: args.status, filter: args.filter, per_page: args.per_page, page: args.page });
    },
  • Zod input schema for github_checks_list_for_suite defining required params (owner, repo, check_suite_id) and optional params (check_name, status, filter, per_page, page).
    inputSchema: z.object({
      owner: z.string().describe("owner"),
      repo: z.string().describe("repo"),
      check_suite_id: z.string().describe("check_suite_id"),
      check_name: z.string().optional().describe("Returns check runs with the specified `name`."),
      status: z.enum(["queued", "in_progress", "completed"]).optional().describe("Returns check runs with the specified `status`."),
      filter: z.enum(["latest", "all"]).optional().describe("Filters check runs by their `completed_at` timestamp. `latest` returns the most recent check runs."),
      per_page: z.number().optional().describe("The number of results per page (max 100). For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\""),
      page: z.number().optional().describe("The page number of the results to fetch. For more information, see \"[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api).\"")
    }),
  • src/index.ts:62-62 (registration)
    Registration of all checks tools (including github_checks_list_for_suite) into the MCP server under the 'checks' category.
    { category: "checks", tools: checksTools },
  • src/index.ts:110-129 (registration)
    Registration loop that registers each tool (including github_checks_list_for_suite) with the MCP server using its name, description, inputSchema, and handler.
    for (const tool of allTools) {
      server.tool(
        tool.name,
        tool.description,
        tool.inputSchema.shape as any,
        async (args: any) => {
          try {
            const result = await tool.handler(args as any);
            return {
              content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (err) {
            const message = err instanceof Error ? err.message : String(err);
            return {
              content: [{ type: "text" as const, text: `Error: ${message}` }],
              isError: true,
            };
          }
        }
      );
  • Helper function githubRequest that handles HTTP calls to the GitHub API, used by the handler to make the GET request to list check runs in a check suite.
    export async function githubRequest<T>(
      method: string,
      path: string,
      body?: Record<string, unknown>,
      params?: Record<string, string | number | boolean | string[] | undefined>
    ): Promise<T> {
      const url = new URL(`${BASE_URL}${path}`);
    
      if (params) {
        for (const [key, value] of Object.entries(params)) {
          if (value === undefined || value === null || value === "") continue;
          if (Array.isArray(value)) {
            url.searchParams.set(key, value.join(","));
          } else {
            url.searchParams.set(key, String(value));
          }
        }
      }
    
      const headers: Record<string, string> = {
        Authorization: `Bearer ${getToken()}`,
        Accept: "application/vnd.github+json",
        "X-GitHub-Api-Version": "2022-11-28",
        "User-Agent": "github-mcp/1.0.0",
      };
    
      if (body) {
        headers["Content-Type"] = "application/json";
      }
    
      const res = await fetch(url.toString(), {
        method,
        headers,
        body: body ? JSON.stringify(body) : undefined,
      });
    
      if (!res.ok) {
        const text = await res.text().catch(() => "");
        let detail = text;
        try {
          const json = JSON.parse(text);
          detail = json.message || text;
          if (json.errors) detail += ` -- ${JSON.stringify(json.errors)}`;
        } catch {}
        throw new Error(`GitHub API error ${res.status}: ${detail}`);
      }
    
      if (res.status === 204) return {} as T;
    
      return res.json() as Promise<T>;
    }
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits like pagination support, filtering options (status, check_name, filter), or the nature of the response. The tool has parameters for filtering and pagination, but the description does not mention them, leaving the agent unaware of these capabilities.

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

Conciseness4/5

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

The description is a single, concise sentence that front-loads the core purpose. While very short, it effectively communicates the essential information without unnecessary words. It could benefit from including key usage details, but for a simple listing operation, it is adequately structured.

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 lack of an output schema and the presence of 8 parameters (including pagination and filtering), the description should have mentioned these aspects to provide a complete picture. It does not explain what is returned or how to interpret the results, leaving significant gaps for the agent.

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

Parameters3/5

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

Schema coverage is 100%, with all 8 parameters having descriptions that explain their purpose (e.g., 'check_name', 'status', 'filter', 'per_page', 'page'). The tool description adds no additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb 'List', the resource 'check runs', and the context 'in a check suite', which differentiates it from sibling tools like github_checks_list_for_ref. The purpose is unambiguous and immediately understandable.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as having a check_suite_id, or comparison with related tools like github_checks_list_for_ref or github_checks_list_suites_for_ref.

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/Eyalm321/github-mcp'

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