Skip to main content
Glama
yogesh-joshi-0333

browser-control-mcp-server

by yogesh-joshi-0333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Browser Extract

browser_extract

Extract structured text or element attributes from a web page without raw HTML. Omit a selector to get visible page text, or provide one to return matching content.

Instructions

Extract structured text or attributes from the page without dumping raw HTML. With no selector, returns the page's visible text content (like a reader view). With a selector, returns the text (or a given attribute) of the matching element(s). Much smaller and more directly useful than browser_get_dom when you just need the content, not the markup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoForce a specific mode. Defaults to extension.
multipleNoIf true, return an array of results for every match instead of just the first (default false).
selectorNoCSS selector to scope extraction to. Omit to extract the whole page's visible text.
attributeNoAttribute to extract instead of text, e.g. "href", "src", "value". Requires selector.
sessionIdNoPuppeteer session ID for headless mode. Skips mode selection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.0

TDQS

A4/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It discloses that output is smaller than raw HTML and how it behaves with/without a selector, but says nothing about permissions, whether it waits for the page to be stable, frame handling, or cost. Adequate but thin for an unannotated read/extract tool.

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 value, then the two selector cases, then the sibling comparison. No filler or repetition.

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?

Complete enough for a 5-param, no-required-params extraction tool with full schema coverage and no output schema: the two selector behaviors and the markup-vs-content tradeoff are covered. Could be richer on mode/session interaction and frame context.

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 parameters are fully documented in schema; baseline 3. The description only elaborates on selector and attribute behavior, adding little beyond what the schema already states for mode, multiple, and sessionId.

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 (extract) and resources (structured text/attributes from page), and explicitly names the sibling it replaces (browser_get_dom) with the distinguishing condition (need content, not markup). An agent can pick this over browser_get_dom without opening either schema.

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

Usage Guidelines4/5

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

Gives clear conditions for both modes: no selector returns visible reader-view text, selector returns element text or attribute. Explicitly contrasts with browser_get_dom. Lacks guidance on when to prefer other extraction siblings (browser_get_element, browser_find) or the mode/session interaction, so not a full 5.

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