Skip to main content
Glama
Sign In
browserless-mcp

browserless-mcp

Official
by browserless
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

browserless_skill

Read-only

Load Browserless agent skills on demand or discover site-specific recipes for a host. Call it as a fallback when a page has non-trivial mechanics like shadow DOM, modals, cookie consent, or captchas.

Instructions

Load a Browserless agent skill on demand, or discover site-specific recipes.

Two uses:

  • { site: "" } — list any site-specific recipes tuned for that host (e.g. { site: "ebay.com" }), returned as pointers. Do this as soon as you know the host you're about to drive; if one matches your task, load it by id. Returns a "no recipe" note when there's none.

  • { id: "" } — load a skill body: an in-house skill id (list below) OR a site recipe id host/slug from a site lookup.

Use the in-house skills below when you suspect the page exhibits a non-trivial mechanic but no SKILL block was auto-injected. The auto-injection heuristics are conservative; calling this tool is the explicit fallback.

Available in-house skills:

  • shadow-dom — deep selectors, iframe URL-pattern syntax, what works through deep-ref

  • cookie-consent — vendor-specific dismiss recipes (OneTrust, Cookiebot, Didomi, etc.)

  • modals — close-button heuristics, ESC handling, alertdialog vs. dialog

  • snapshot-misses — truncated/empty snapshots, image-rendered content

  • dynamic-content — choosing the right wait* method after async triggers

  • screenshots — when to screenshot vs. snapshot, scope and format choices

  • vision-fallback — click by coordinate when a "< " deep selector still can't surface the element (shadow DOM, nested iframe, canvas)

  • tabs — multi-tab workflows, peek-without-switching

  • autonomous-login — load before authenticating: when the user asked you to log in, when a wall blocks the task, or as soon as a password input appears. Covers the don't-login-by-default posture, contextual credential matching, MFA/captcha branches, and how to report the outcome.

  • autonomous-registration — load before creating an account: when the user asked you to sign up / register, or as soon as a Create-account form appears. Covers the don't-register-by-default posture, identity and credential-sink rules, save-first-then-loadSecret password handling, the emailed-code branch, and how to report the outcome.

  • captchas — the solve command, response semantics, escalation path (Cloud-only)

  • file-transfers — uploadFile / getDownloads, stdio-path vs. base64 content, size caps

  • profile-import — import the user's local Chrome/Brave/Edge sign-ins as a profile with the Browserless CLI (consent-gated; only when running on the user's machine)

Input Schema

NameRequiredDescriptionDefault
idNoThe skill to load: an in-house skill id (see tool description) OR a site recipe id "host/slug" returned by a prior `site` lookup.
siteNoA page host (e.g. "ebay.com"). Lists any site-specific recipes tuned for that host as pointers — then load one with its id.
_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.16.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare this is a read-only, non-destructive, non-open-world operation. The description goes further by explaining what each mode returns (recipe pointers, a "no recipe" note, or a skill body) and by enumerating the available in-house skill ids, which is essential behavioral context for selecting the right id.

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?

The description is long but well structured: it front-loads the two use cases, then provides the skill catalogue as a necessary reference because the schema has no enum. Every section serves a purpose, and the bulleted skill list is directly actionable rather than filler.

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?

There is no output schema, but the description explains return shapes for both modes (pointers, "no recipe" note, skill body). Combined with the skill catalogue and mode semantics, an agent has everything needed to call the tool correctly without additional documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds substantial meaning beyond the schema: `site` returns recipe pointers to be loaded later by id, and `id` accepts either an in-house skill id or a `host/slug` recipe id. The two-mode dispatch and examples (`{ site: "ebay.com" }`) make the parameters unambiguous.

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 first line states a specific action and resource: loading a Browserless agent skill or discovering site-specific recipes. It explicitly splits the tool into two modes (`site` lookup vs. `id` load), making it immediately distinguishable from the sibling browser-automation tools.

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?

The description gives explicit when-to-use guidance: do a `site` lookup as soon as the host is known, load a matching recipe by id, and treat this tool as the explicit fallback when auto-injection heuristics miss a non-trivial mechanic. It also names per-skill triggers (e.g., load `autonomous-login` before authenticating, `autonomous-registration` before signup) that leave little to inference.

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