MCP Web Tools
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 |
|---|---|
| web_extractB | Extract structured content from a URL: title, headings, paragraphs, links, images, and metadata |
| web_searchA | Search the web using DuckDuckGo and return structured results with titles, URLs, and snippets |
| web_monitorA | Check if a website is up, measure response time, and get HTTP details |
| html_to_markdownA | Convert HTML content or a URL to clean, readable markdown. Removes scripts, styles, and navigation. |
| web_multi_extractA | Extract content from multiple URLs in parallel. Returns results for each URL. |
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 5 tools
web_extract and web_multi_extract are clearly related, with the latter being just a parallel variant, and html_to_markdown overlaps with web_extract for URL-to-content conversion. Search and monitor are clearly distinct, but the extraction/convert boundary could cause misselection.
Most tools follow web_<action>, but html_to_markdown breaks the prefix pattern and uses a different target_to_target style. The pair web_extract/web_multi_extract is consistent, but overall naming conventions are mixed.
Five tools is a well-scoped size for a web utility server, covering search, monitoring, extraction, and conversion without unnecessary bloat. Each tool earns its place, though the single vs. multi extract duplication is minor.
The toolkit covers core web operations: search, availability/response checking, single-URL and multi-URL extraction, and HTML-to-markdown conversion. Minor gaps exist (e.g., no URL validation or site traversal), but agents can accomplish common web tasks without dead ends.