Skip to main content
Glama
cutlerbenjamin1-cmd

web-explorer

by cutlerbenjamin1-cmd
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

fx

Bypass bot protection (Cloudflare, Datadome) using an anti-detect Firefox browser. Perform actions like navigate, read, click, fill, and extract to handle JavaScript challenges and persistent sessions.

Instructions

Anti-detect Firefox browser. Use when web(crawl) fails due to bot protection (Cloudflare, Datadome, Reddit verification). Persistent profile at data/fx_profile/: cookies, localStorage, and solved Cloudflare challenges survive MCP reboots. Fast defaults: images blocked, humanize off, domcontentloaded wait. Prefer 'read' for one-shot extraction — auto-waits for JS challenges (networkidle), runs trafilatura, auto-closes. Supports harvest=True to save content to disk instead of loading into context. Use 'navigate' + explicit actions for multi-step workflows (logged-in flows, form fills, clicks); call 'close' when done. Actions: navigate, read, click, fill, type, screenshot, extract, text, wait, press, scroll, evaluate, cookies, add_cookies, close, status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX scroll amount
yNoY scroll amount
keyNoKey for press action (Enter, Tab, etc.)
urlNoURL for navigate/read action
textNoText for fill/type actions
stateNoWait state for wait action
actionYesBrowser action to perform
scriptNoJavaScript for evaluate action
cookiesNoCookies for add_cookies action
harvestNoFor read action: save raw HTML to harvested/<harvest_dest>/ (converted to markdown by harvester). Saves context tokens.
stealthNoEnable humanized cursor movement (up to 1.5s/action). Only affects new sessions. Default: false.
summaryNoFor read action: trafilatura summary mode (fast, ~5KB cap). False = full extraction (~15KB). Default: true.
timeoutNoAction timeout in seconds (default: 300)
visibleNoShow browser window. Only affects new sessions. Default: false.
selectorNoCSS selector for element actions
full_pageNoFull page screenshot (default: false)
wait_untilNoNavigation wait condition. Default: domcontentloaded. read action upgrades to networkidle unless explicitly overridden.
close_afterNoFor read action: auto-close session after extraction. Default: true.
load_imagesNoAllow images to load. Needed for screenshots with visuals. Only affects new sessions. Default: false.
harvest_destNoFor read action: subfolder under harvested/ (e.g., 'fx/'). Required when harvest=true.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Discloses persistence, default settings (images blocked, humanize off), waiting behavior (auto-waits for JS challenges), and side effects (harvest saves to disk). Without annotations, it fully carries the transparency burden and does so thoroughly.

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 description is moderately lengthy but efficient, front-loading the purpose and then detailing actions and parameters. Every sentence adds value, though it could be slightly tighter in grouping related information.

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 complex tool with 20 parameters and no output schema, the description covers major actions, defaults, and use cases well. It lacks explicit return value descriptions for some actions (e.g., screenshot, status), but overall provides sufficient completeness for effective use.

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?

All 20 parameters are described in the schema (100% coverage). The description adds meaningful context, such as explaining the roles of 'read' and 'navigate', and clarifying defaults for wait_until and stealth. This enhances understanding beyond the raw schema.

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?

Clearly identifies as 'Anti-detect Firefox browser' with a specific use case (when web crawl fails due to bot protection). Distinguishes itself from sibling tools like 'web' by offering browser-level automation with anti-detection features.

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?

Provides explicit guidance on when to use: 'Use when web(crawl) fails due to bot protection'. Differentiates between 'read' for one-shot extraction and 'navigate' for multi-step workflows, and advises when to call 'close'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cutlerbenjamin1-cmd/web-explorer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server