Skip to main content
Glama

delete_project

Remove GitHub projects to clean up your workspace and manage repositories efficiently. This tool deletes projects using their unique project ID.

Instructions

Delete a GitHub project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes

Implementation Reference

  • Core handler method in ProjectManagementService that executes the delete_project tool logic. Validates input implicitly via schema, calls repository delete, and formats success response.
    async deleteProject(data: {
      projectId: string;
    }): Promise<{ success: boolean; message: string }> {
      try {
        await this.projectRepo.delete(data.projectId);
        return {
          success: true,
          message: `Project ${data.projectId} has been deleted`,
        };
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • Repository implementation that performs the actual GitHub GraphQL deleteProjectV2 mutation to delete the project.
    async delete(id: ProjectId): Promise<void> {
      const mutation = `
        mutation($input: DeleteProjectV2Input!) {
          deleteProjectV2(input: $input) {
            projectV2 {
              id
            }
          }
        }
      `;
    
      await this.graphql(mutation, {
        input: {
          projectId: id,
        },
      });
    }
  • Tool definition including schema, description, and examples for delete_project tool.
    export const deleteProjectTool: ToolDefinition<DeleteProjectArgs> = {
      name: "delete_project",
      description: "Delete a GitHub project",
      schema: deleteProjectSchema as unknown as ToolSchema<DeleteProjectArgs>,
      examples: [
        {
          name: "Delete project",
          description: "Delete a GitHub project by ID",
          args: {
            projectId: "PVT_kwDOLhQ7gc4AOEbH"
          }
        }
      ]
    };
  • Registration of the deleteProjectTool in the ToolRegistry during initialization.
    this.registerTool(updateProjectTool);
    this.registerTool(deleteProjectTool);
  • Top-level tool dispatcher in MCP server that routes delete_project calls to the service handler.
    case "delete_project":
      return await this.service.deleteProject(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete' implies a destructive, irreversible mutation, but the description doesn't specify permissions required, whether deletion is permanent or recoverable, rate limits, or what happens to associated items (e.g., issues, milestones). For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable. Every word ('Delete', 'a', 'GitHub', 'project') earns its place by specifying the operation and target.

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 destructive nature, lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't address critical context like permissions, irreversibility, error conditions, or effects on related data. For a deletion tool in a project management context, this leaves too many unknowns for safe and effective use.

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 description coverage is 0%, so the description must compensate for undocumented parameters. The description mentions 'a GitHub project', which hints that 'projectId' refers to a GitHub project identifier, but doesn't clarify format (e.g., numeric ID, URL slug) or where to find it. It adds minimal meaning beyond the schema's property name, partially compensating for the coverage gap.

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 action ('Delete') and resource ('a GitHub project'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'update_project' or 'get_project' by specifying a destructive operation. However, it doesn't explicitly differentiate from 'delete_milestone' or other deletion tools in terms of scope or hierarchy.

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. It doesn't mention prerequisites (e.g., needing admin permissions), consequences (e.g., irreversible deletion), or when to choose 'delete_project' over other tools like 'remove_project_item' or 'update_project' with status changes. Usage is implied only by the tool name.

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/HarshKumarSharma/MCP'

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