Skip to main content
Glama
Sign In
EvannZhongg

BrowserAttach

by EvannZhongg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_fetch

Read a URL’s main document through an existing signed-in browser profile in a temporary background tab, then close it. Fetch page text, HTML, or JSON without launching a separate automation browser.

Instructions

Read a URL's main document using the profile's sign-in in a temporary background tab, then close it. Site scripts run and may affect other tabs. status/ok describe HTTP only (unknown=null); readiness/degradation are separate. body is a string. next_cursor reads immutable cache without revisiting; up to 4 captures per connection/profile.

Input Schema

NameRequiredDescriptionDefault
urlNoHTTP(S), no URL credentials; required unless cursor is supplied.
cursorNoContinuation accepts only browser_id, cursor and max_chars.
formatNoDefault rendered text; html=current DOM (dom=rendered); json=validated JSON.
max_charsNoText/HTML page budget; capture_truncated marks source loss. JSON returns whole, ignores this budget, errors above 1M chars.
browser_idYes
timeout_msNoDefault 15000; total including creation/cleanup, reserving capture time after unmet waits.
wait_untilNoDefault load; network_idle waits for load then 500ms without observed requests. Unmet waits return a degraded capture if readable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.24.2
    • changedInput schema / properties / format / description
      Previous value: -"Default text (rendered); html=current DOM with dom=rendered; json=complete validated JSON."New value: +"Default rendered text; html=current DOM (dom=rendered); json=validated JSON."
    • changedInput schema / properties / max_chars / description
      Previous value: -"Text/HTML page budget; JSON ignores this and returns whole, up to 1M chars. capture_truncated means text/HTML loss; oversized JSON errors."New value: +"Text/HTML page budget; capture_truncated marks source loss. JSON returns whole, ignores this budget, errors above 1M chars."
    • changedInput schema / properties / timeout_ms / description
      Previous value: -"Default 15000; total deadline including creation/cleanup, with time reserved for capture after an unmet wait."New value: +"Default 15000; total including creation/cleanup, reserving capture time after unmet waits."
  2. First observedv0.24.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the temporary tab that is closed, the side effect that site scripts may affect other tabs, the distinction between HTTP status and readiness/degradation, and the capture limit. It omits auth-failure or error behavior detail, so it is not exhaustive.

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?

The purpose is front-loaded in the first sentence, and every subsequent sentence carries distinct information. The telegraphic style ('status/ok describe HTTP only') is dense but not wasteful.

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 exists, so the description must explain returns; it covers status/ok, readiness/degradation, body-as-string, and cursor semantics but does not describe the overall response shape or error outcomes. Adequate but with clear gaps for a 7-parameter fetch tool.

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 86%, so the baseline is 3; the description earns a bump by explaining that next_cursor reads an immutable cache without revisiting and that body is a string, adding meaning beyond the schema's cursor and max_chars descriptions.

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?

The description gives a specific verb and resource ('Read a URL's main document') and adds the mechanism ('temporary background tab') plus profile sign-in, which distinguishes it from a plain navigation tool. It stops short of naming a sibling such as browser_navigate or browser_read_text for contrast.

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?

Usage is implied by the mechanics: it fetches a main document with the profile's credentials and returns text/html/json, and the cursor sentence implies pagination continuation. There is no explicit when-to-use/when-not guidance and no named alternative among the many browser_* siblings.

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