Skip to main content
Glama
Sign In
BrowserSolver MCP Server

BrowserSolver MCP Server

Official
by browsersolver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Website WebUnlocker

website_webunlocker
Read-only

Fetches HTML from whitelisted retail and marketplace hosts to solve persistent bot challenges that still block rendering after standard attempts.

Instructions

Website WebUnlocker. BrowserSolver's highest HTML fetch tier for retail and marketplace hosts on your account whitelist. Solves persistent bot challenges that still block Rendering. Credit cost: 3 credits per call.

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": {
      "query": "<query>"
    },
    "name": "website_webunlocker"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPublic URL to fetch with the WebUnlocker tier. Include http:// or https://. The hostname must be on your BrowserSolver whitelist.
fieldsNoComma-separated list of fields to keep in the response, with dot notation for nested fields (e.g. name,location.city). Does not change the credit cost.
allow_redirectsNoWhether the unlock session should chase HTTP redirects. Default: true.
return_page_sourceNoChoose between processed markup and the exact post-unlock source. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, open world), and the description adds genuinely new behavior: a credit cost of 3 per call, the account-whitelist requirement, and the fact that this is a recovery tier for failed Rendering attempts. It does not describe return payload shape beyond processed vs raw source.

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 identity and tier positioning, followed by the constraint and the cost. Every sentence carries unique information with no filler.

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 single-URL fetch tool with no output schema and fully documented parameters, the description covers purpose, scope, cost, and escalation context. Only a brief note on response format would improve it.

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% and each parameter (query, fields, allow_redirects, return_page_source) is documented in the schema with defaults and semantics. The description adds nothing parameter-specific, so the baseline of 3 applies.

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 names a specific resource (HTML fetch) and a precise tier ('highest HTML fetch tier'), and explicitly scopes it to retail/marketplace hosts on a whitelist. It also distinguishes itself from the sibling website_rendering by saying it solves challenges that still block Rendering.

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 gives clear conditions for use: retail/marketplace hostnames that must be on the whitelist, and cases where Rendering is still blocked. It stops short of explicitly naming website_antibot or website_rendering as fallbacks with a when-not-to-use statement.

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

Deploy Server

Other Tools