Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

deleteTunnel

Terminates an active TestingBot tunnel using its tunnel ID to close the connection and stop local or private-site access through that tunnel.

Instructions

Delete an active TestingBot tunnel by its ID. This will terminate the tunnel connection.

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": {
      "tunnelId": "<tunnelId>"
    },
    "name": "deleteTunnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
tunnelIdYesThe tunnel ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden; it does disclose the consequential effect ('terminate the tunnel connection'), which is meaningful for a destructive operation. It omits irreversibility, what happens if the ID is unknown or the tunnel is already closed, and whether any associated resources are released.

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?

Two short sentences with the action front-loaded and the consequence immediately following; nothing is padded. The second sentence is slightly redundant with 'Delete' but still earns its place by naming the terminated connection.

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 delete with full schema coverage and no output schema, this is minimally adequate. It leaves unresolved the boundary with 'stopTunnel' and the failure modes of deleting a non-existent or inactive tunnel, which matter for a destructive call with no annotations.

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%, so the single 'tunnelId' parameter is already documented with its accepted number/string types. The description adds only 'by its ID', which restates the schema rather than clarifying format, source, or lookup method.

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?

The description names a specific verb and resource ('Delete an active TestingBot tunnel') plus the identifier used to target it, so the action is unambiguous. It does not, however, distinguish this from the sibling 'stopTunnel', which an agent could easily confuse with deletion.

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?

The word 'active' hints that the tunnel must currently be running, but there is no explicit when-to-use statement, no prerequisite framing, and no guidance on choosing this over 'stopTunnel' or 'getTunnelList'. The agent must infer the selection criteria entirely.

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