Skip to main content
Glama
debugg-ai

Debugg AI MCP

Official
by debugg-ai

Delete Project

delete_project

Permanently delete a project and all associated environments, credentials, and test history using its UUID. This action cannot be undone and returns an error if the project does not exist.

Instructions

Delete a project by UUID. Returns {deleted:true, uuid}. DESTRUCTIVE — removes the project and its associated environments, credentials, and test history. No undo. Returns isError:true + NotFound when already deleted or uuid doesn't exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesUUID of the project to delete. Required.

Implementation Reference

  • Main handler function that executes the delete_project tool logic. Creates a DebuggAIServerClient, calls deleteProject, returns success or handles 404/errors.
    export async function deleteProjectHandler(
      input: DeleteProjectInput,
      _context: ToolContext,
    ): Promise<ToolResponse> {
      const start = Date.now();
      logger.toolStart('delete_project', { uuid: input.uuid });
    
      try {
        const client = new DebuggAIServerClient(config.api.key);
        await client.init();
    
        try {
          await client.deleteProject(input.uuid);
          logger.toolComplete('delete_project', Date.now() - start);
          return {
            content: [{ type: 'text', text: JSON.stringify({ deleted: true, uuid: input.uuid }, null, 2) }],
          };
        } catch (err: any) {
          if (err?.statusCode === 404 || err?.response?.status === 404) return notFound(input.uuid);
          throw err;
        }
      } catch (error) {
        logger.toolError('delete_project', error as Error, Date.now() - start);
        throw handleExternalServiceError(error, 'DebuggAI', 'delete_project');
      }
    }
  • Zod schema definition for DeleteProjectInput (uuid: z.string().uuid()) and the inferred type.
    export const DeleteProjectInputSchema = z.object({
      uuid: z.string().uuid(),
    }).strict();
    export type DeleteProjectInput = z.infer<typeof DeleteProjectInputSchema>;
  • Tool definition: name='delete_project', title, description, and inputSchema. Also the validated variant that wires schema + handler together.
    export function buildDeleteProjectTool(): Tool {
      return {
        name: 'delete_project',
        title: 'Delete Project',
        description: DESCRIPTION,
        inputSchema: {
          type: 'object',
          properties: {
            uuid: { type: 'string', description: 'UUID of the project to delete. Required.' },
          },
          required: ['uuid'],
          additionalProperties: false,
        },
      };
    }
  • tools/index.ts:34-45 (registration)
    Tool registry: buildDeleteProjectTool() and buildValidatedDeleteProjectTool() are called in initTools() to register the tool.
    export function initTools(ctx: ProjectContext | null): void {
      const tools: Tool[] = [
        buildTestPageChangesTool(ctx),
        buildTriggerCrawlTool(ctx),
        buildProbePageTool(),
        buildSearchProjectsTool(),
        buildSearchEnvironmentsTool(),
        buildCreateEnvironmentTool(),
        buildUpdateEnvironmentTool(),
        buildDeleteEnvironmentTool(),
        buildUpdateProjectTool(),
        buildDeleteProjectTool(),
  • Service-layer helper that performs the actual HTTP DELETE request to the API endpoint api/v1/projects/{uuid}/.
    public async deleteProject(uuid: string): Promise<void> {
      if (!this.tx) throw new Error('Client not initialized — call init() first');
      await this.tx.delete(`api/v1/projects/${uuid}/`);
    }
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses that the operation is destructive, removes associated entities, has no undo, and returns errors for non-existent UUIDs.

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?

Three concise sentences that front-load the action and key warnings. Every sentence adds value.

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

Completeness5/5

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

For a single-parameter destructive deletion tool with no output schema, the description fully covers purpose, side effects, error behavior, and safety warnings.

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 clear description for uuid parameter. Description adds no additional parameter semantics beyond the schema, so baseline 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?

Clearly states 'Delete a project by UUID', specifying the action and resource. Distinguishes from sibling deletion tools like delete_environment and delete_test_case.

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

Usage Guidelines4/5

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

Explicitly warns of destructiveness and no undo, and describes error behavior for not found. However, does not provide explicit guidance on when to use this tool versus alternatives.

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/debugg-ai/debugg-ai-mcp'

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