Skip to main content
Glama
browserless

browserless-mcp

Official
by browserless
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

browserless_performance

Read-only

Run a Lighthouse audit on any URL to score performance, accessibility, best practices, PWA, and SEO, then save the full JSON report outside the conversation.

Instructions

Run a Lighthouse performance audit on any URL via the Browserless /performance API. Returns scores and metrics for accessibility, best practices, performance, PWA, and SEO. Optionally filter by category, emulate a mobile or desktop device, supply a custom Lighthouse config, or supply performance budgets. Returns category scores inline and saves the full JSON report outside the conversation. Use the local path (stdio) or download URL (HTTP) to inspect only the audits you need. Note: audits can take 30s–120s depending on the site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to audit (must be http or https)
configNoCustom Lighthouse config object, sent as the /performance "config" field. Defaults to { extends: "lighthouse:default" }. "categories" and "device" override the matching keys in config.settings. See https://github.com/GoogleChrome/lighthouse/blob/main/docs/configuration.md
deviceNoDevice to emulate during the audit: "mobile" or "desktop". Applies Lighthouse's matching form factor, screen size, network/CPU throttling and user agent. Omit for the Lighthouse default (mobile).
_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.
budgetsNoLighthouse performance budgets array. See https://developer.chrome.com/docs/lighthouse/performance/performance-budgets
profileNoOptional name of an authentication profile to hydrate into the browser before the Lighthouse audit runs. 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 (audits can take 30s–120s)
categoriesNoLighthouse categories to audit: "accessibility", "best-practices", "performance", "pwa", "seo". Omit for all categories.

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 Lighthouse audit runs. 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 Lighthouse audit runs. 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. Changed2 schema fields changedv1.36.0
    • addedInput schema / properties / config
      Added value: +{
+  "additionalProperties": {},
+  "description": "Custom Lighthouse config object, sent as the /performance \"config\" field. Defaults to { extends: \"lighthouse:default\" }. \"categories\" and \"device\" override the matching keys in config.settings. See https://github.com/GoogleChrome/lighthouse/blob/main/docs/configuration.md",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedInput schema / properties / device
      Added value: +{
+  "description": "Device to emulate during the audit: \"mobile\" or \"desktop\". Applies Lighthouse's matching form factor, screen size, network/CPU throttling and user agent. Omit for the Lighthouse default (mobile).",
+  "enum": [
+    "mobile",
+    "desktop"
+  ],
+  "type": "string"
+}
  3. First observedv1.16.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description goes further, disclosing the 30s–120s latency, that category scores are returned inline while the full JSON report is saved outside the conversation, and that the profile parameter requires a pre-existing profile for the API token. This is meaningful behavioral context beyond structured fields.

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?

Front-loaded with the core action, followed by returns, options, output location, and a caveat. Each sentence carries information, though it is on the longer side; nothing is clearly redundant.

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?

No output schema exists, but the description explains what is returned inline versus saved out-of-band and how to retrieve the full report. For an 8-parameter tool with nested objects and covered annotations, this is close to complete, missing only explicit sibling routing.

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 each parameter is already documented in-schema. The description restates the optional knobs (category filter, device emulation, custom config, budgets) but adds no syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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 ('Run a Lighthouse performance audit on any URL via the Browserless /performance API') and enumerates what it returns (accessibility, best practices, performance, PWA, SEO scores). This is clearly distinguishable from siblings like browserless_search, browserless_crawl, or browserless_function without opening the schema.

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 implies usage through its return list and the note about inspecting audits via the local path or download URL, but it never states when to reach for this tool over related siblings (e.g. browserless_export or browserless_live_url). The latency note hints at when it may be inappropriate, which is useful but not framed as guidance.

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