Skip to main content
Glama
Sign In

Hyperbrowser

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Hyperbrowser Scrape

hyperbrowser_scrape
Read-onlyIdempotent

Scrape a single web page from a cloud browser and return clean content (markdown, html, links, and page metadata). Handles JS-rendered pages. Example: hyperbrowser_scrape({ url: "https://example.com", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://example.com/page",
      "_apiKey": "your-hyperbrowser-api-key"
    },
    "name": "hyperbrowser_scrape"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full URL to scrape, e.g. "https://example.com/page"
_apiKeyYesHyperbrowser API key. Sign up at https://app.hyperbrowser.ai (docs: https://docs.hyperbrowser.ai/).
formatsNoOutput formats to include. Any of "markdown", "html", "links". Default ["markdown"].
onlyMainContentNoIf true, strip nav/footer/ads and return only the main article content. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds behavioral value by noting it 'Handles JS-rendered pages' and lists return formats (markdown, html, links, page metadata). This goes beyond what annotations provide, though it doesn't cover error scenarios or rate limits. No contradiction.

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?

Two sentences and an example pack the purpose, outputs, and JS-rendering capability with zero waste. Purpose is front-loaded, and the example is a useful compact demonstration. No redundant content.

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?

With no output schema, the description compensates by stating return formats (markdown, html, links, page metadata) and JS-rendering support. It covers what an agent needs to invoke the tool correctly. It omits potential edge cases (e.g., rate limits, authentication details) but these are minor given annotations and schema.

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 coverage is 100%, so parameter descriptions already fully document url, _apiKey, formats, and onlyMainContent. The description adds an example call that illustrates usage but does not deepen semantic understanding beyond the schema. Baseline 3 is appropriate given full schema coverage.

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 function: 'Scrape a single web page from a cloud browser and return clean content' with explicit output types. It differentiates from siblings by emphasizing 'single web page' (versus crawl) and 'clean content' (versus extract). The example reinforces the purpose.

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 for single-page scraping but does not explicitly contrast with sibling tools like hyperbrowser_crawl or hyperbrowser_extract. It provides an example but lacks when-to-use vs when-not-to-use guidance. The 'single web page' hint is present but not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hyperbrowser toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources