Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Create Remote Browser

createRemoteBrowser

Registers a remote browser for real-browser monitors by storing its WebSocket URL and name. Monitor pages once the browser ID is assigned to a monitor's remote_browser field.

Instructions

Adds a remote browser. Real-browser monitors use it once their remote_browser field is set to its ID. Check the URL first with testRemoteBrowser.

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": {
      "name": "<name>",
      "url": "<url>"
    },
    "name": "createRemoteBrowser"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWebSocket endpoint, e.g. ws://browserless:3000?token=…
nameYesA name to tell it apart
includeSecretsNoReturn credentials in full instead of "***"; they then stay in the transcript. Default: false, or UPTIME_KUMA_INCLUDE_SECRETS.

Output Schema

NameRequiredDescriptionDefault
okYes
remoteBrowserNo
remoteBrowserIDNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is supplied. The description adds useful domain context that the returned ID becomes a foreign key for monitors, but says nothing about duplicate creation, permission requirements, or failure modes when the WebSocket endpoint is invalid.

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, front-loaded with what the tool does, then the downstream dependency, then the prerequisite check. No redundant restatement of the name or schema and nothing that could be cut.

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?

An output schema exists, so return values need no explanation, and all three parameters are fully documented. The description covers purpose, prerequisite validation, and the reference relationship that makes the tool useful. Only edge cases such as duplicate URL/name handling are absent.

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%, including the WebSocket URL pattern, the name field, and the includeSecrets transcript caveat, so the schema carries parameter meaning. The description only indirectly touches the url parameter by pointing to the test tool; it adds no syntax or constraint detail beyond the schema.

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?

"Adds a remote browser" gives a specific verb and resource, and the follow-up sentence explains where the created object fits (monitors reference it via remote_browser). It never explicitly contrasts with updateRemoteBrowser or deleteRemoteBrowser, but the creation verb plus the ID-reference explanation makes the intent unambiguous.

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 states a concrete prerequisite: validate the endpoint with testRemoteBrowser before creating, naming a real sibling tool. It also implies the situation in which you need this (before attaching a real-browser monitor). It stops short of stating exclusions or what to do if a browser with the same URL already exists.

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