Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

deleteBuild

Deletes a build and all its associated tests by build ID, removing the build record and its test data from TestingBot.

Instructions

Delete a build and all its associated tests by build ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "buildId": "<buildId>"
    },
    "name": "deleteBuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildIdYesThe build ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the important cascade effect (associated tests are deleted too), which is real value beyond the schema, but it says nothing about irreversibility, required permissions, or what happens when the build ID doesn't exist.

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?

One sentence, front-loaded with the action and the destructive scope, with no redundant or filler wording.

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

Completeness3/5

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

For a one-parameter destructive tool with no annotations and no output schema, the description covers what is removed but omits whether the deletion is permanent and whether test results, screenshots, or reports tied to those tests are also lost. Adequate but with a meaningful gap for a destructive operation.

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% and the single buildId parameter is already documented in the schema, so the description only restates 'by build ID'. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb ('Delete') and resource ('a build') plus the cascade scope ('all its associated tests'), which clearly separates it from deleteTest or deleteStorageFile. It doesn't explicitly name a sibling or contrast behavior, so it stops short of full differentiation.

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?

There is no when-to-use or when-not-to-use guidance, no mention of an alternative for deleting a single test versus a whole build, and no stated prerequisites. The agent must infer from the name and siblings when this is the right call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.