Spicrawl

Live view link for a remote browser

spicrawl_browser_live_view

Gets a link a person can open to watch the remote browser your CDP connection is driving, and take control of it: the same tabs, cookies and page. Use it when a page needs a human: a login, a one-time code, a captcha. Send them live_view_url; they press "Take control", do the step, and give control back. While they have it, your connection's input and navigation commands fail with error -32001 (reading the page still works); poll spicrawl_browser_control (action status) until controller is agent, then carry on. The link works once and must be opened within 60 seconds; ask again for a new one. The session must still be connected. Watching costs nothing beyond the session itself.

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": {
      "session_id": "<session_id>"
    },
    "name": "spicrawl_browser_live_view"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	The remote browser session, as `session_id` from spicrawl_browser_connect_url. It exists while that connection is open.

Output Schema

Name	Required	Description
`live_url`	No	The bare live-view WebSocket, for building your own viewer.
`expires_in`	No	Seconds the link stays valid if not opened (60).
`session_id`	Yes	The remote browser session.
`single_use`	No	Always true.
`live_view_url`	Yes	A page a person opens in their browser to watch and take control. Single use, open within 60 s.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Goes well beyond the supplied annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing the single-use link, the 60-second open window, the prerequisite that the session must still be connected, and the exact error code the agent will hit while a human holds control. The only minor gap is that it does not say whether the returned link grants the human any destructive or extended capabilities beyond the visible browser.

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?

Front-loaded with what the tool does, then the trigger, then the operational handoff sequence, then constraints and cost. Every sentence carries operational content: error code, polling target, expiry, session condition, and cost. 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?

For a single-parameter handoff tool with an output schema, the description covers the full agent loop: request the link, hand it over, expect -32001 on input, poll status, resume when `controller` is `agent`. Nothing an agent needs to invoke and recover correctly is missing.

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?

The single parameter is fully documented in the schema (100% coverage, binding it to `session_id` from `spicrawl_browser_connect_url`), so the baseline is 3. The description adds meaning by stating the session must still be connected, which tells the agent the identifier is only valid for the lifetime of an open connection.

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: gets a link a person can open to watch and take control of the remote browser driven by the CDP connection. It specifies the exact artifact returned (`live_view_url`) and the same-tabs/cookies/page continuity, which distinguishes it from session or control siblings.

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

Usage Guidelines5/5

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

Gives explicit when-to-use triggers (login, one-time code, captcha) and names the companion tool and action to poll (`spicrawl_browser_control` action `status`) until `controller` is `agent`. It also states the failure condition (-32001 on input/navigation while a human holds control) and what still works.

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

All Spicrawl tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?