Skip to main content
Glama
TCSoftInc

TestCollab MCP Server

by TCSoftInc

delete_test_plan

Permanently delete a test plan and its execution data from TestCollab using the test plan ID. This action removes all related testing resources.

Instructions

Delete a test plan from TestCollab.

WARNING: This permanently deletes the test plan and related execution data.

Required: id (test plan ID) Optional: project_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTest plan ID to delete (required)
project_idNoProject ID (optional if TC_DEFAULT_PROJECT is set)

Implementation Reference

  • The handler function for deleting a test plan, which resolves the project ID, calls the API client, and formats the response.
    export async function handleDeleteTestPlan(args: {
      id: number;
      project_id?: number;
    }): Promise<{ content: Array<{ type: "text"; text: string }> }> {
      try {
        const projectId = resolveProjectId(args.project_id);
        if (!projectId) {
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify({
                  error: {
                    code: "MISSING_PROJECT_ID",
                    message:
                      "No project_id provided and no default project configured. Set TC_DEFAULT_PROJECT or pass project_id.",
                  },
                }),
              },
            ],
          };
        }
    
        const client = getApiClient();
        const result = await client.deleteTestPlan(args.id, projectId);
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                success: true,
                deleted_test_plan_id: args.id,
                result,
              }),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({
                error: {
                  code: "DELETE_TEST_PLAN_FAILED",
                  message:
                    error instanceof Error ? error.message : "Unknown error",
                },
              }),
            },
          ],
        };
      }
    }
  • Zod schema for validating the input arguments for the delete_test_plan tool.
    export const deleteTestPlanSchema = z.object({
      id: z.number().describe("Test plan ID to delete (required)"),
      project_id: z
        .number()
        .optional()
        .describe("Project ID (optional if TC_DEFAULT_PROJECT is set)"),
    });
  • Tool definition containing name and description for the delete_test_plan tool.
    export const deleteTestPlanTool = {
      name: "delete_test_plan",
      description: `Delete a test plan from TestCollab.
    
    WARNING: This permanently deletes the test plan and related execution data.
    
    Required: id (test plan ID)
    Optional: project_id`,
    };
Behavior4/5

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

No annotations provided, so description carries full burden. Effectively discloses destructive nature ('permanently deletes') and scope of impact ('related execution data'). Missing: error behavior, auth requirements, or idempotency details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three-sentence structure is front-loaded: purpose first, critical warning second, parameters third. Parameter sentence is slightly redundant given schema completeness, but warning earns its place for a destructive operation.

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

Completeness4/5

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

Adequate for a 2-parameter destructive operation without output schema. Safety warning addresses primary risk. Could improve by clarifying what 'related execution data' specifically includes or mentioning if deletion is cascading.

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 has 100% description coverage with required/optional status already defined. Description lists parameters but adds no semantic value beyond schema (actually omits the TC_DEFAULT_PROJECT condition mentioned in schema). Baseline score for high schema coverage.

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?

Description opens with specific verb 'Delete' + resource 'test plan' + system 'TestCollab'. Clearly distinguishes from sibling tools like delete_suite (different resource) and update_test_plan (different action).

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

Usage Guidelines3/5

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

WARNING about permanent deletion implies when NOT to use (when data preservation is needed), but lacks explicit comparison to alternatives like update_test_plan or guidance on prerequisites.

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/TCSoftInc/testcollab-mcp-server'

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