web-shooter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crawlA | Crawl a site from a start page, following the links most relevant to |
| fetchA | Read one or more web pages or PDFs (URLs, or local PDF paths) as clean markdown. With |
| linksA | List a page's links. With |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
crawl and links both surface URLs from a page's links, which could initially confuse an agent, but descriptions clearly separate site-wide discovery (crawl) from single-page link listing/ranking (links), and fetch is unambiguously for reading content. Boundaries are mostly clear.
Two tools use verb-style names (crawl, fetch) while links is a noun, a minor deviation from a single convention. All are single-word, lowercase, and immediately readable, so the inconsistency is small.
Three tools is exactly right for a web-reading server: discover (crawl), list/rank links (links), and read content (fetch). Each earns its place with no redundancy.
The core lifecycle of find-then-read is covered, including PDFs, JS-rendered pages, robots.txt compliance, and query-based relevance filtering. Minor gaps exist (no explicit sitemap or multi-URL batch crawl options), but agents can work around them by chaining crawl and fetch.