Skip to main content
Glama
browserless

browserless-mcp

Official
by browserless
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

browserless_export

Read-only

Export a webpage from a URL and return its native format—HTML, PDF, image, or more—with automatic content-type detection. Optionally bundle CSS, JS, and images into a ZIP for offline use.

Instructions

Export a webpage from a URL via the Browserless /export API. Fetches the URL and returns its content in the native format (HTML, PDF, image, etc.). Automatically detects the content type. Set includeResources=true to bundle all page assets (CSS, JS, images) into a ZIP archive for offline use.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to export (must be http or https)
_promptNoThe 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.
profileNoOptional name of an authentication profile to hydrate into the browser before the page is exported. The profile's cookies, localStorage, and IndexedDB are restored into the session before the request runs. The profile must already exist for the API token in use — create one with Browserless.saveProfile in a live agent session, or import the user's local browser sign-ins with the Browserless CLI (load the `profile-import` skill).
timeoutNoRequest timeout in milliseconds
bestAttemptNoWhen true, proceed even if awaited events fail or timeout.
gotoOptionsNoPuppeteer Page.goto() options for navigation
waitForTimeoutNoMilliseconds to wait after page load before exporting
includeResourcesNoWhen true, bundle all linked resources (CSS, JS, images) into a ZIP file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.39.0
    • changedInput schema / properties / profile / description
      Previous value: -"Optional name of an authentication profile to hydrate into the browser before the page is exported. The profile's cookies, localStorage, and IndexedDB are restored into the session before the request runs. The profile must already exist for the API token in use — create one with Browserless.saveProfile in a live agent session first."New value: +"Optional name of an authentication profile to hydrate into the browser before the page is exported. The profile's cookies, localStorage, and IndexedDB are restored into the session before the request runs. The profile must already exist for the API token in use — create one with Browserless.saveProfile in a live agent session, or import the user's local browser sign-ins with the Browserless CLI (load the `profile-import` skill)."
  2. First observedv1.16.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: automatic content-type detection and what includeResources actually produces (a ZIP of CSS/JS/images). It omits auth/profile requirements, rate limits, and error behavior, which are left to the schema.

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 tight sentences, front-loaded with the core action and endpoint, followed by return behavior and the one optional flag that changes output. 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?

With no output schema, the description usefully explains what comes back (native HTML/PDF/image, auto-detected) and the ZIP variant, which is the main ambiguity for this tool. Auth/profile setup and error semantics are only covered in the schema, so it is not fully self-sufficient but is adequate for an 8-param read-only tool.

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%, so the baseline is 3. The description restates includeResources and its ZIP effect, which the schema already documents, and adds nothing about profile, timeout, bestAttempt, or gotoOptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (export a webpage from a URL) plus the underlying /export API, and clarifies the returned content type. It differentiates itself implicitly from extraction/crawl siblings by emphasizing native-format export rather than structured extraction, though it never names an alternative tool.

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

Usage Guidelines3/5

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

The description gives one actionable usage cue (set includeResources=true to bundle assets for offline use) but offers no when-to-use vs when-not guidance and no routing against siblings like browserless_smartscraper or browserless_crawl. Usage is implied rather than stated.

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