Skip to main content
Glama

github_apps_delete_installation

Delete a GitHub App installation for the authenticated app by providing the installation ID.

Instructions

Delete an installation for the authenticated app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
installation_idYesinstallation_id

Implementation Reference

  • The handler function that executes the tool logic: sends a DELETE request to /app/installations/{installation_id} to delete a GitHub App installation.
    handler: async (args: Record<string, any>) => {
      return githubRequest("DELETE", `/app/installations/${args.installation_id}`, undefined, undefined);
    },
  • Input schema defining that the tool requires an installation_id string parameter.
    inputSchema: z.object({
      installation_id: z.string().describe("installation_id")
    }),
  • The tool is defined as an entry in the appsTools array in src/tools/apps.ts. It is re-exported via src/tools/index.ts and registered with the MCP server in src/index.ts.
    {
      name: "github_apps_delete_installation",
      description: "Delete an installation for the authenticated app",
      inputSchema: z.object({
        installation_id: z.string().describe("installation_id")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("DELETE", `/app/installations/${args.installation_id}`, undefined, undefined);
      },
    },
  • The githubRequest helper function used by the handler to make authenticated HTTP requests to the GitHub API.
    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 provided, the description carries full burden. It only states the action without disclosing side effects, irreversibility, or associated resource impacts. For a destructive operation, this is insufficient.

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 sentence with no wasted words, perfectly concise and front-loaded.

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

Completeness3/5

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

Given the tool's simplicity (1 parameter, no output schema), the description is minimally adequate. However, it lacks contextual details like irreversibility or prerequisites, which would be beneficial for a deletion tool.

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%, so baseline is 3. The parameter description 'installation_id' is tautological, and the tool description adds no additional meaning beyond the schema.

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 'Delete an installation for the authenticated app', specifying the verb (Delete), resource (installation), and context (for the authenticated app). This clearly distinguishes it from siblings like suspend or authorization deletion.

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, such as suspend or unsuspend installation. No prerequisites, permissions, or contextual hints are given.

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