Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Delete Remote Browser

deleteRemoteBrowser
Destructive

Permanently deletes a remote browser; real-browser monitors using it are kept and fall back to built-in Chromium. Find the ID with listRemoteBrowsers.

Instructions

Permanently deletes a remote browser. Real-browser monitors that used it are kept and fall back to the built-in Chromium. Find the ID with listRemoteBrowsers.

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": {
      "remoteBrowserID": "<remoteBrowserID>"
    },
    "name": "deleteRemoteBrowser"
  }
}

Input Schema

NameRequiredDescriptionDefault
remoteBrowserIDYesThe ID of the remote browser to delete

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely non-obvious downstream behavior: dependent real-browser monitors survive and fall back to the built-in Chromium, which is exactly the kind of side-effect context annotations cannot express. It stops short of stating what happens on a nonexistent or already-deleted ID.

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?

Three short sentences, each doing distinct work: the action, the consequential side effect, and the ID lookup route. The most important fact (permanent deletion) is front-loaded with no filler.

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

Completeness5/5

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

With rich annotations and an output schema present, the description does not need to restate return values or safety flags. It covers the remaining gaps an agent would actually have — permanence, collateral effect on monitors, and ID discovery — for a one-parameter destructive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single required parameter, so the baseline is already satisfied by structured data. The description still earns credit by explaining how to obtain the remoteBrowserID via listRemoteBrowsers, adding a procedural hint the schema does not contain.

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?

States a specific verb and resource ('Permanently deletes a remote browser'), which is unambiguous and cleanly separates it from the delete* siblings operating on API keys, monitors, tags, etc. An agent knows exactly what object this acts on without opening the schema.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite path: 'Find the ID with listRemoteBrowsers,' which routes the agent to the sibling it needs first. It lacks explicit when-not-to-use guidance (e.g., updating instead of deleting), but the destructive nature of the operation makes the intent clear.

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