Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

deleteStorageFile

Deletes a file from TestingBot storage by its app_url, letting you clean up uploaded apps and remove obsolete artifacts.

Instructions

Delete a file from TestingBot storage using its app_url.

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": {
      "appUrl": "<appUrl>"
    },
    "name": "deleteStorageFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
appUrlYesThe app_url of the file to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for a destructive operation, yet it never says the deletion is permanent/irreversible, what happens if the appUrl does not exist, or whether any permissions or confirmation are required. It discloses only the lookup key used to target the file.

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?

One short sentence with the action front-loaded and no filler. It is efficient, though the brevity comes at the cost of omitting behavioral context rather than because the information is complete.

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

Completeness2/5

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

For an irreversible mutation with no annotations and no output schema, the definition should say what confirmation or preconditions exist and what failure looks like. Neither is covered, leaving an agent unable to judge consequences of calling it.

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 description coverage is 100% and the single appUrl parameter is already documented as 'The app_url of the file to delete'. The description's 'using its app_url' adds no format, sourcing, or validation detail beyond the schema, so the baseline 3 applies.

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 file from TestingBot storage') plus the identifying key (app_url). An agent can distinguish it from getStorageFiles and uploadFile by name alone, though the description does not explicitly name those alternatives.

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?

No guidance on when to use this versus the storage-listing or upload tools, and no prerequisites such as needing to look up the appUrl via getStorageFiles first. The only implied usage is that deletion requires an existing app_url.

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