Skip to main content
Glama
browserless

browserless-mcp

Official
by browserless
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

browserless_skill

Read-only

Load browser automation skills on demand: discover site-specific recipes for a host or load in-house skills for handling pop-ups, cookies, dynamic content, and more.

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

  • 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 the required final JSON response shape.

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

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

Input Schema

TableJSON 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.

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's role is lighter. It adds context about returns ('no recipe' note, pointers) and that it loads skill bodies. No contradictions with annotations.

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?

Well-structured with two main uses and bullet points for in-house skills. Front-loaded with key information. Slightly lengthy due to detailed skill list, but each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so description should explain return values. It mentions 'returned as pointers' and 'load a skill body', but lacks explicit details on response format. Adequate but not fully complete.

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?

Schema coverage is 100%, baseline 3. The description adds meaning: explains the difference between id and site parameters, provides examples, and clarifies the _prompt parameter's intended use. This goes beyond the schema descriptions.

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 clearly states the tool's purpose: 'Load a Browserless agent skill on demand, or discover site-specific recipes.' It distinguishes between two use cases (site and id) and differentiates from sibling tools by focusing on skill loading rather than other browserless actions.

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?

Explicit guidance is provided: 'Use the in-house skills below when you suspect the page exhibits a non-trivial mechanic but no SKILL block was auto-injected.' Also advises to use site lookup 'as soon as you know the host' and lists specific scenarios for each in-house skill, making when-to-use clear.

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/browserless/browserless-mcp'

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