Delete a TestRail test case by its unique ID to remove obsolete or incorrect cases from your project. Provide the case_id parameter to permanently delete it.
Delete a test case
| Name | Required | Description | Default |
|---|---|---|---|
| case_id | Yes | Test case ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description is the only source of behavioral context, but it only says deletion occurs. It does not disclose irreversibility, cascading effects on tests or results, or permission requirements for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is minimal and front-loaded, with no filler. It is appropriately sized for a simple single-parameter deletion tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The one-line description is enough to understand the basic operation, but with no annotations and no output schema, a destructive tool like this needs at least a warning about permanence or side effects. The lack of any caveat leaves an agent without enough context for safe selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents case_id. The description adds no parameter-level information; the baseline 3 applies because the schema carries the burden.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action and resource: 'Delete a test case.' It clearly distinguishes the singular delete_case from the sibling delete_cases.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool instead of alternatives. There is no mention of delete_cases for bulk deletion or any exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.