Skip to main content
Glama
debugg-ai

Debugg AI MCP

Official
by debugg-ai

Delete Test Suite

delete_test_suite

Disable a test suite to hide it from default list queries without permanent removal. Accepts suite UUID or name with project identifier.

Instructions

Disable (soft-delete) a test suite. The suite and its tests are hidden from default list queries but not permanently removed. Accepts suiteUuid directly, or suiteName + project identifier for name-based lookup. Returns {deleted: true, suiteUuid}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suiteUuidNoTest suite UUID. Provide suiteUuid OR (suiteName + project identifier).
suiteNameNoTest suite name (case-insensitive exact match). Requires projectUuid or projectName.
projectUuidNoProject UUID. Provide projectUuid OR projectName.
projectNameNoProject name (case-insensitive exact match). Provide projectUuid OR projectName.

Implementation Reference

  • Main handler for delete_test_suite tool. Accepts DeleteTestSuiteInput, resolves project/suite by name or UUID, and calls client.disableTestSuite() to soft-delete the suite. Returns {deleted: true, suiteUuid} on success.
    export async function deleteTestSuiteHandler(
      input: DeleteTestSuiteInput,
      _context: ToolContext,
    ): Promise<ToolResponse> {
      const start = Date.now();
      logger.toolStart('delete_test_suite', input);
      try {
        const client = new DebuggAIServerClient(config.api.key);
        await client.init();
    
        let suiteUuid = input.suiteUuid;
        if (!suiteUuid) {
          let projectUuid = input.projectUuid;
          if (!projectUuid) {
            const resolved = await resolveProject(client, input.projectName!);
            if ('error' in resolved) return errorResp(resolved.error, resolved.message, { candidates: (resolved as any).candidates });
            projectUuid = resolved.uuid;
          }
          const resolved = await resolveTestSuite(client, input.suiteName!, projectUuid);
          if ('error' in resolved) return errorResp(resolved.error, resolved.message, { candidates: (resolved as any).candidates });
          suiteUuid = resolved.uuid;
        }
    
        await client.disableTestSuite(suiteUuid);
        logger.toolComplete('delete_test_suite', Date.now() - start);
        return { content: [{ type: 'text', text: JSON.stringify({ deleted: true, suiteUuid }, null, 2) }] };
      } catch (error) {
        logger.toolError('delete_test_suite', error as Error, Date.now() - start);
        throw handleExternalServiceError(error, 'DebuggAI', 'delete_test_suite');
      }
    }
  • Zod schema DeleteTestSuiteInputSchema — combines suiteIdentifier (suiteUuid?, suiteName?) and projectIdentifier (projectUuid?, projectName?) and validates with .strict(). Also exports type DeleteTestSuiteInput.
    export const DeleteTestSuiteInputSchema = z.object({
      ...suiteIdentifier,
      ...projectIdentifier,
    }).strict();
    
    export type DeleteTestSuiteInput = z.infer<typeof DeleteTestSuiteInputSchema>;
  • Suite identifier partial schema used by delete_test_suite and other suite tools: suiteUuid (optional UUID) and suiteName (optional string min 1).
    const suiteIdentifier = {
      suiteUuid: z.string().uuid().optional(),
      suiteName: z.string().min(1).optional(),
    };
  • Tool definition buildDeleteTestSuiteTool() builds the Tool object with name 'delete_test_suite', title, description, and inputSchema. buildValidatedDeleteTestSuiteTool() wraps it with the Zod schema and handler.
    // ── delete_test_suite ─────────────────────────────────────────────────────────
    
    export function buildDeleteTestSuiteTool(): Tool {
      return {
        name: 'delete_test_suite',
        title: 'Delete Test Suite',
        description: 'Disable (soft-delete) a test suite. The suite and its tests are hidden from default list queries but not permanently removed. Accepts suiteUuid directly, or suiteName + project identifier for name-based lookup. Returns {deleted: true, suiteUuid}.',
        inputSchema: {
          type: 'object',
          properties: {
            ...SUITE_PROPS,
            ...PROJECT_PROPS,
          },
          additionalProperties: false,
        },
      };
    }
    
    export function buildValidatedDeleteTestSuiteTool(): ValidatedTool {
      return { ...buildDeleteTestSuiteTool(), inputSchema: DeleteTestSuiteInputSchema, handler: deleteTestSuiteHandler };
    }
  • tools/index.ts:50-96 (registration)
    Tool registration in the main tools array (line 50) and validated tools array (line 72) which are used to initialize the server's tool registry.
        buildDeleteTestSuiteTool(),
        buildCreateTestCaseTool(),
        buildUpdateTestCaseTool(),
        buildDeleteTestCaseTool(),
        buildRunTestSuiteTool(),
        buildGetTestSuiteResultsTool(),
      ];
      const validated: ValidatedTool[] = [
        buildValidatedTestPageChangesTool(ctx),
        buildValidatedTriggerCrawlTool(ctx),
        buildValidatedProbePageTool(),
        buildValidatedSearchProjectsTool(),
        buildValidatedSearchEnvironmentsTool(),
        buildValidatedCreateEnvironmentTool(),
        buildValidatedUpdateEnvironmentTool(),
        buildValidatedDeleteEnvironmentTool(),
        buildValidatedUpdateProjectTool(),
        buildValidatedDeleteProjectTool(),
        buildValidatedSearchExecutionsTool(),
        buildValidatedCreateProjectTool(),
        buildValidatedCreateTestSuiteTool(),
        buildValidatedSearchTestSuitesTool(),
        buildValidatedDeleteTestSuiteTool(),
        buildValidatedCreateTestCaseTool(),
        buildValidatedUpdateTestCaseTool(),
        buildValidatedDeleteTestCaseTool(),
        buildValidatedRunTestSuiteTool(),
        buildValidatedGetTestSuiteResultsTool(),
      ];
    
      _tools = tools;
      _validatedTools = validated;
    
      toolRegistry.clear();
      for (const v of validated) toolRegistry.set(v.name, v);
    }
    
    export function getTools(): Tool[] {
      if (!_tools) initTools(null);
      return _tools!;
    }
    
    export function getTool(name: string): ValidatedTool | undefined {
      if (!_validatedTools) initTools(null);
      return toolRegistry.get(name);
    }
Behavior5/5

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

Without annotations, the description fully discloses the soft-delete behavior, including that tests are hidden but not removed, and that the suite is not permanently deleted. It also specifies the return format (`{deleted: true, suiteUuid}`), ensuring the agent understands the outcome.

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 two sentences, each serving a distinct purpose: first defines the action and its effect, second explains parameter alternatives and return value. No unnecessary words or redundancy.

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?

Given no output schema, the description sufficiently covers the return value. It explains the soft-delete nature, which is critical for an agent to understand the tool's consequences. All parameter combinations are addressed, and the lack of required parameters is clear from the schema.

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

Parameters4/5

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

The input schema has 100% description coverage for all four parameters. The description adds value by clarifying the two identification strategies (direct vs. name-based) and noting case-insensitive exact matching for names, which is not explicit in 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 the tool performs a soft-delete (disable) on a test suite, distinguishing it from other delete tools like delete_project or delete_test_case. It specifies that both the suite and its tests are hidden but not permanently removed.

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?

The description explains two identification methods (direct UUID or name-based lookup) and the required parameters for each. While it doesn't explicitly state when to use one over the other or provide exclusions, it is sufficient for the agent to infer usage based on available parameter combinations.

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