Spicrawl

Browser (CDP) connect URL

spicrawl_browser_connect_url

Coming soon: remote browsers are not available yet, so minting fails; do not rely on this tool. For scripted page interaction today use actions on spicrawl_scrape. Mints a single-use connect URL for Spicrawl's remote browser (GET /v1/browser, Chrome DevTools Protocol) so YOUR code can drive it with puppeteer.connect({ browserWSEndpoint }) or playwright.chromium.connectOverCDP(url). It calls POST /v1/browser/token and returns a ws:// or wss:// URL carrying a short-lived token, never the API key: the URL works ONCE, within 60 seconds, and only with the options given here (editing them in the URL is refused), so call this right before connecting and again for every new session. Prefer sending the key as an Authorization header when the client supports headers on the upgrade (playwright connectOverCDP(url, { headers }), puppeteer.connect({ browserWSEndpoint, headers })): then connect to the plain /v1/browser URL with 'Authorization: Bearer ' and no token is needed. The endpoint exists only when the deployment was installed with --with-cdp, and the key must carry the browser scope; otherwise minting fails (404 or 403). Parameter errors are reported when minting.

Input Schema

TableJSON Schema

Name	Required	Description
`proxy`	No	Your own proxy, as http://user:pass@host:port. Replaces our pool, so proxy_country, proxy_region and sticky_key cannot be combined with it. Kept out of the returned URL.
`engine`	No	Browser engine. Default: the deployment's default (chromium). 'obscura' cannot run headful.
`headless`	No	false = headful browser with a display (desktop-sized screen). Omit for the deployment default.
`sticky_key`	No	Keep one exit IP for the session under this key (2-64 letters, digits, hyphens). Omit to rotate (the default).
`session_ttl`	No	Session lifetime in seconds, 60-900. Default 180.
`proxy_region`	No	Broader exit region/pool name; 'global' means no constraint. Mutually exclusive with proxy_country.
`proxy_country`	No	Exit country, ISO-3166 alpha-2 lowercase (e.g. 'de'). Mutually exclusive with proxy_region.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (readOnly/openWorld/idempotent/destructive), the description discloses that the URL is single-use, expires in 60 seconds, carries a short-lived token and never the API key, that baked-in options cannot be edited without refusal, and that minting fails with 404/403 unless the deployment has --with-cdp and the key holds the `browser` scope. This is exactly the kind of behavioral context annotations cannot convey.

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

Conciseness4/5

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

The most important fact (unavailable today, use an alternative) is front-loaded, which is the right structural choice. It is long and dense, but nearly every clause earns its place by covering expiry, token handling, prerequisites, and the header alternative.

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 7-param, no-required, no-output-schema tool, the description covers the return value shape (ws:// or wss:// URL with token), lifetime, one-time-use constraint, auth requirements, and deployment/scope prerequisites. Nothing an agent needs to call it 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?

Schema coverage is 100%, so the schema already documents all seven parameters — baseline 3. The description adds meaning beyond the schema by explaining that the options supplied at mint time are frozen into the URL and cannot be changed afterward, which tells the agent to choose parameters carefully rather than edit the returned URL.

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?

The description states a specific verb and resource — mints a single-use CDP connect URL for Spicrawl's remote browser — and names both the endpoint (GET /v1/browser) and the sibling alternative (`actions` on spicrawl_scrape). An agent can distinguish it from the session/batch siblings without opening any schema.

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?

It gives explicit when-not guidance up front ('remote browsers are not available yet... do not rely on this tool'), names the alternative for today (`actions` on spicrawl_scrape), and describes an alternate invocation mode (Authorization header on plain /v1/browser) with the condition that selects it.

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?