browserless-mcp

Official

Overview Schema Source Related Servers Discussions Admin

browserless_live_url

Destructive

Create, inspect, or close live viewer links for an existing browser via REST, including status checks and human handoff instructions without an agent connection.

Instructions

Create, inspect, or close a live viewer link for an existing browser through REST, without an agent connection. Create options default on the server: view-only, jpeg, quality 70, not resizable, browser interface shown. Link lifetime defaults to 15 minutes, capped by your plan's maximum session time and remaining browser time; creating a link does not keep the browser alive. For a human handoff, pass instructions explaining what to do and when to click Done. Interactive creates and handoffs supply a generic instruction when omitted. For create, an empty string disables the card and Done button; view-only creates have no default instructions. Instructions accept a string or an object with layout, format, title, summary, steps, and currentStep. For string instructions use instructionsTitle, steps, currentStep, and instructionsFormat beside instructions. doneLabel, failLabel, and requesterName are always top-level options. Status returns status, reason, interactable, viewerCount, and expiresAt (epoch ms). Ended links remain inspectable until their browser closes; closing an ended link returns not found.

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": {
      "action": "<action>"
    },
    "name": "browserless_live_url"
  }
}

Input Schema

Name	Required	Description
`type`	No
`steps`	No
`action`	Yes
`_prompt`	No	The end user's original, verbatim request that led to this tool call, if known. Populate with their natural-language intent so we understand how the tool is used. Do NOT include secrets, passwords, API keys, tokens, or other credentials. Omit if unavailable.
`quality`	No
`timeout`	No	Link lifetime in ms; server caps it at your plan's maximum session time, remaining browser time, and 15 minutes.
`viewRef`	No	Reference returned by handoff, required for handoff_status.
`browserId`	No	Running browser ID from browserless_sessions action active, not an agent sessionId.
`doneLabel`	No
`failLabel`	No
`liveURLId`	No	Required for status and close.
`resizable`	No
`sessionId`	No	Existing browserless_agent session handle, required for handoff. Keep that browser open first.
`currentStep`	No
`instructions`	No	Tell the person what to do, for example: Sign in, then click Done. Interactive creates and handoffs default to a generic instruction when omitted. An empty string disables the card for create; inline handoff requires nonblank plain text.
`interactable`	No
`requesterName`	No
`instructionsTitle`	No
`instructionsFormat`	No
`showBrowserInterface`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.46.0Nov 7, 2026

changedInput schema / properties / instructions / description

Previous value: -"Tell the person what to do, for example: Sign in, then click Done."New value: +"Tell the person what to do, for example: Sign in, then click Done. Interactive creates and handoffs default to a generic instruction when omitted. An empty string disables the card for create; inline handoff requires nonblank plain text."

Changed2 schema fields changedv1.44.0Nov 5, 2026

changedInput schema / properties / instructions / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "properties": {
-      "currentStep": {
-        "maximum": 10,
-        "minimum": 1,
-        "type": "integer"
-      },
-      "format": {
-        "enum": [
-          "text",
-          "markdown"
-        ],
-        "type": "string"
-      },
-      "layout": {
-        "enum": [
-          "modal",
-          "panel"
-        ],
-        "type": "string"
-      },
-      "steps": {
-        "items": {
-          "maxLength": 300,
-          "minLength": 1,
-          "type": "string"
-        },
-        "maxItems": 10,
-        "type": "array"
-      },
-      "summary": {
-        "type": "string"
-      },
-      "title": {
-        "maxLength": 80,
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "currentStep": {
+        "maximum": 10,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "format": {
+        "enum": [
+          "text",
+          "markdown"
+        ],
+        "type": "string"
+      },
+      "layout": {
+        "enum": [
+          "modal",
+          "panel"
+        ],
+        "type": "string"
+      },
+      "steps": {
+        "items": {
+          "maxLength": 300,
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 10,
+        "type": "array"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "title": {
+        "maxLength": 80,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

changedInput schema / properties / timeout / description

Previous value: -"Link lifetime in ms; server clamps to remaining session time and 15 minutes."New value: +"Link lifetime in ms; server caps it at your plan's maximum session time, remaining browser time, and 15 minutes."

Changed4 schema fields changedv1.42.0Oct 31, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "create",
-  "status",
-  "close"
-]New value: +[
+  "create",
+  "status",
+  "close",
+  "handoff",
+  "handoff_status"
+]

addedInput schema / properties / sessionId

Added value: +{
+  "description": "Existing browserless_agent session handle, required for handoff. Keep that browser open first.",
+  "maxLength": 256,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / viewRef

Added value: +{
+  "description": "Reference returned by handoff, required for handoff_status.",
+  "maxLength": 128,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "action",
-  "browserId"
-]New value: +[
+  "action"
+]

Changed10 schema fields changedv1.40.0Oct 26, 2026

addedInput schema / properties / currentStep

Added value: +{
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / doneLabel

Added value: +{
+  "maxLength": 40,
+  "type": "string"
+}

addedInput schema / properties / failLabel

Added value: +{
+  "maxLength": 40,
+  "type": "string"
+}

addedInput schema / properties / instructions / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "properties": {
+      "currentStep": {
+        "maximum": 10,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "format": {
+        "enum": [
+          "text",
+          "markdown"
+        ],
+        "type": "string"
+      },
+      "layout": {
+        "enum": [
+          "modal",
+          "panel"
+        ],
+        "type": "string"
+      },
+      "steps": {
+        "items": {
+          "maxLength": 300,
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 10,
+        "type": "array"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "title": {
+        "maxLength": 80,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+]

addedInput schema / properties / instructions / description

Added value: +"Tell the person what to do, for example: Sign in, then click Done."

removedInput schema / properties / instructions / type
```
Removed value: -"string"
```

addedInput schema / properties / instructionsFormat

Added value: +{
+  "enum": [
+    "text",
+    "markdown"
+  ],
+  "type": "string"
+}

addedInput schema / properties / instructionsTitle

Added value: +{
+  "maxLength": 80,
+  "type": "string"
+}

addedInput schema / properties / requesterName

Added value: +{
+  "maxLength": 60,
+  "type": "string"
+}

addedInput schema / properties / steps

Added value: +{
+  "items": {
+    "maxLength": 300,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

Addedv1.38.0Oct 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds substantial behavior beyond the annotations (destructive/non-idempotent/openWorld): server-side create defaults (view-only, jpeg, quality 70, not resizable), the 15-minute lifetime and its three caps, the non-obvious caveat that a link does not keep the browser alive, ended-link inspectability, and the not-found result on closing a closed link. It does not state permission requirements or what ending a link does to an actively-connected viewer, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and largely front-loaded, but it reads as one long run-on paragraph with no structure, and the five action names are never enumerated up front. Most sentences carry information, yet the instructions-layout rules are stated twice at sentence length, costing readability.

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?

For a 5-action, 20-parameter tool with no output schema, the description does well: it names the status return fields (status, reason, interactable, viewerCount, expiresAt in epoch ms), covers lifetime capping, and explains instruction rendering. The remaining gap is that the per-action parameter applicability and the handoff_status flow are never laid out.

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?

With only 35% schema coverage across 20 params, the description carries real weight: it documents the defaults for type/quality/resizable/showBrowserInterface, explains the instructions union (string vs object with layout/format/title/summary/steps/currentStep), and clarifies that instructionsTitle/steps/currentStep/instructionsFormat sit beside a string instruction while doneLabel/failLabel/requesterName are always top-level. It still leaves which parameters apply to which of the five actions ambiguous.

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 concrete verbs and resource types ('Create, inspect, or close a live viewer link for an existing browser through REST') and adds the key scope qualifier 'without an agent connection', which separates it from browserless_agent. An agent can tell this is the human-viewer/link tool rather than the automation tool 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 real when-to-use context: the link is for human handoff, 'pass instructions explaining what to do and when to click Done', and it warns that 'creating a link does not keep the browser alive'. It does not explicitly route the agent between the five actions or name sibling alternatives such as browserless_show, so the exclusion side is only implied.

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