Skip to main content
Glama
ddukbg

GitHub Enterprise MCP Server

delete-repository

Permanently remove a GitHub Enterprise repository by specifying the owner and repository name. Requires confirmation to execute deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner
repoYesRepository name
confirmYesConfirmation for deletion (must be true)

Implementation Reference

  • The MCP tool handler for 'delete-repository'. Validates owner and repo parameters, requires confirm=true flag for safety, calls the repository API's deleteRepository method, and returns success or error response in MCP format.
    async ({ owner, repo, confirm }) => {
      try {
        // Parameter validation
        if (!owner || typeof owner !== 'string' || owner.trim() === '') {
          return {
            content: [
              {
                type: "text",
                text: "Repository owner is required."
              }
            ]
          };
        }
    
        if (!repo || typeof repo !== 'string' || repo.trim() === '') {
          return {
            content: [
              {
                type: "text",
                text: "Repository name is required."
              }
            ]
          };
        }
    
        if (!confirm) {
          return {
            content: [
              {
                type: "text",
                text: "You must set 'confirm' to true to delete a repository. This action is irreversible."
              }
            ]
          };
        }
    
        await context.repository.deleteRepository(owner, repo);
    
        return {
          content: [
            {
              type: "text",
              text: `Successfully deleted repository: ${owner}/${repo}`
            }
          ]
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text",
              text: `Error deleting repository: ${error.message}`
            }
          ]
        };
      }
    }
  • Zod input schema defining parameters for the delete-repository tool: owner (string), repo (string), confirm (boolean required for safety).
    {
      owner: z.string().min(1).describe("Repository owner"),
      repo: z.string().min(1).describe("Repository name"),
      confirm: z.boolean().describe("Confirmation for deletion (must be true)")
  • MCP server.tool registration for the 'delete-repository' tool, specifying the tool name, input schema, and handler function.
    server.tool(
      "delete-repository",
      {
        owner: z.string().min(1).describe("Repository owner"),
        repo: z.string().min(1).describe("Repository name"),
        confirm: z.boolean().describe("Confirmation for deletion (must be true)")
      },
      async ({ owner, repo, confirm }) => {
        try {
          // Parameter validation
          if (!owner || typeof owner !== 'string' || owner.trim() === '') {
            return {
              content: [
                {
                  type: "text",
                  text: "Repository owner is required."
                }
              ]
            };
          }
    
          if (!repo || typeof repo !== 'string' || repo.trim() === '') {
            return {
              content: [
                {
                  type: "text",
                  text: "Repository name is required."
                }
              ]
            };
          }
    
          if (!confirm) {
            return {
              content: [
                {
                  type: "text",
                  text: "You must set 'confirm' to true to delete a repository. This action is irreversible."
                }
              ]
            };
          }
    
          await context.repository.deleteRepository(owner, repo);
    
          return {
            content: [
              {
                type: "text",
                text: `Successfully deleted repository: ${owner}/${repo}`
              }
            ]
          };
        } catch (error: any) {
          return {
            content: [
              {
                type: "text",
                text: `Error deleting repository: ${error.message}`
              }
            ]
          };
        }
      }
    );
  • Helper method in RepositoryAPI class that performs the actual GitHub API DELETE request to remove the specified repository.
     * Delete repository
     */
    async deleteRepository(owner: string, repo: string): Promise<void> {
      await this.client.delete(`repos/${owner}/${repo}`);
    }
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