Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Update Remote Browser

updateRemoteBrowser
DestructiveIdempotent

Updates a remote browser's name or WebSocket URL while keeping omitted fields unchanged; pass the full ws:// or wss:// URL, as masked URLs are rejected to protect stored tokens.

Instructions

Changes a remote browser's name or URL; what you leave out keeps its stored value. To change the URL pass it in full: a URL with "***" in it is refused, since it would overwrite the stored token. 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": "updateRemoteBrowser"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoNew ws:// or wss:// endpoint, in full
nameNoNew name
includeSecretsNoReturn credentials in full instead of "***"; they then stay in the transcript. Default: false, or UPTIME_KUMA_INCLUDE_SECRETS.
remoteBrowserIDYesThe ID of the remote browser to change

Output Schema

NameRequiredDescriptionDefault
okYes
remoteBrowserNo
remoteBrowserIDYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare this is a destructive, idempotent mutation. The description adds important behavior beyond that: omitted fields are preserved, URLs must be supplied in full, and URLs containing '***' are refused to avoid overwriting the stored token.

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?

The description is front-loaded with the core action and contains no wasted sentences. Each detail—omission semantics, full URL requirement, '***' refusal, and ID lookup—earns its place.

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

Completeness4/5

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

With an output schema, full parameter descriptions, and annotations covering safety characteristics, the description is nearly complete. It could more explicitly warn about the destructive nature of updates or mention includeSecrets, but those are secondary given the structured metadata.

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%, so the baseline is 3. The description adds meaning beyond the schema by explaining partial-update behavior for name and URL and the special refusal rule for masked tokens. The includeSecrets parameter is left to the schema description.

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 states a specific verb and resource: changing a remote browser's name or URL. It is clearly an update operation, though it does not explicitly distinguish itself from sibling operations like createRemoteBrowser or deleteRemoteBrowser.

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?

It explains partial-update semantics, says omitted fields keep stored values, and directs the agent to listRemoteBrowsers to find the ID. It does not state when not to use this tool, but the usage context is clear.

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