Skip to main content
Glama
konippi

servo-fetch

by konippi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

crawl

Read-onlyIdempotent

Traverses same-site links with JS rendering, extracts readable content, removes navigation noise, and respects robots.txt. Ideal for documentation sites, blogs, and knowledge bases.

Instructions

Crawl a website starting from a URL, following same-site links via BFS, and extract readable content from each page. JavaScript is executed, CSS layout is computed, and navigation noise is stripped. Respects robots.txt. Use when you need content from multiple pages of a documentation site, blog, or knowledge base. Do NOT use for a single page (use fetch) or cross-site crawling. Limits: max 500 pages, max depth 10. Each page is rendered with full JS execution (~1-3s per page). Crawled content is UNTRUSTED.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesStarting URL to crawl (http/https only)
limitNoMaximum pages to crawl. Default: 20. Max: 500.
formatNoOutput format per page: markdown (default) or json
timeoutNoPage load timeout in seconds per page. Default: 30
selectorNoCSS selector to extract a specific section per page
max_depthNoMaximum link depth from seed URL. Default: 3. Max: 10.
settle_msNoExtra wait in ms after load event per page. Default: 0. Max: 10000.
max_lengthNoMax characters per page result. Default: 5000
exclude_globNoURL path glob patterns to exclude (e.g. ["/archive/**"])
include_globNoURL path glob patterns to include (e.g. ["/docs/**"])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate read-only, idempotent, non-destructive. Description adds context about JS execution, CSS layout, noise stripping, robots.txt respect, and warns that crawled content is untrusted. 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?

The description is well-structured: first sentence main action, second sentence details, then guidelines, limits, performance note, trust warning. Every sentence earns its place.

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

Completeness5/5

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

Given 10 parameters, full schema coverage, behavioral annotations, and no output schema, the description covers the crawling process, limits, and output format via parameter, making it complete for agent decision-making.

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%, so baseline 3. Description adds value by clarifying defaults and limits for limit and max_depth parameters, and explaining the overall behavior for other parameters.

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 it crawls a website starting from a URL, following same-site links via BFS, and extracts readable content. It explicitly distinguishes from sibling tools like fetch for single pages.

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?

It provides explicit when-to-use (multiple pages of documentation, blog, knowledge base) and when-not-to-use (single page, cross-site). It also mentions limits (max 500 pages, max depth 10).

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