Skip to main content
Glama
Sign In

Hyperbrowser

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Hyperbrowser Crawl

hyperbrowser_crawl
Read-onlyIdempotent

Crawl a website starting from a URL, following links and scraping each page to markdown. Use maxPages to bound the crawl. Example: hyperbrowser_crawl({ url: "https://example.com", maxPages: 10, _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",
      "_apiKey": "your-hyperbrowser-api-key",
      "maxPages": 10
    },
    "name": "hyperbrowser_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe starting URL to crawl, e.g. "https://example.com".
_apiKeyYesHyperbrowser API key. Sign up at https://app.hyperbrowser.ai (docs: https://docs.hyperbrowser.ai/).
maxPagesNoMaximum number of pages to crawl. Default 10.
followLinksNoWhether to follow links found on crawled pages. 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 the tool read-only, idempotent, and non-destructive. The description adds meaningful behavioral context: it follows links, scrapes each page to markdown, and uses maxPages as a boundary. This goes beyond what annotations alone provide, though it does not mention potential cost/size caveats or domain-scoping behavior.

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 concise sentences front-load the core purpose, then provide a concrete invocation example. Every sentence contributes value, and the example makes invocation clearer without padding.

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?

For a simple four-parameter tool with strong annotations and 100% schema coverage, the description is sufficient for an agent to select and invoke it correctly. It explains the crawl behavior, output format (markdown), and bounding parameter. It could add return-format details since there is no output schema, but that is not essential for invocation.

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 the schema already documents all four parameters. The description adds an example call and reinforces maxPages as a bounding control, but it does not add material meaning beyond what the input schema already states. A baseline 3 is appropriate.

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 names a specific action ('Crawl'), a resource ('a website starting from a URL'), and the mechanism ('following links and scraping each page to markdown'). This makes it clearly distinguishable from sibling tools like hyperbrowser_scrape (single-page) and hyperbrowser_extract (structured extraction), even without naming them explicitly.

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 use case is implied by the verb 'crawl' and the link-following behavior, which suggests it is for multi-page site crawling rather than single-page scraping. However, there is no explicit guidance about when to prefer this over hyperbrowser_scrape/hyperbrowser_extract, nor any when-not-to-use conditions. The maxPages note is parameter guidance, not tool-selection guidance.

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