Websearch MCP Server
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| websearch_fetch_pageA | Fetch a URL and return its content as clean markdown. Uses html-to-markdown for high-performance conversion that dramatically reduces token usage. |
| websearch_searchA | Search the web using DuckDuckGo and return results as a markdown list. |
| websearch_search_and_fetchA | Search the web and fetch top result pages as markdown. Combines search + fetch in one call for efficiency. |
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
The tools are mostly distinct with clear purposes: websearch_search for search results, websearch_fetch_page for fetching specific URLs, and websearch_search_and_fetch as a combined operation. However, websearch_search_and_fetch overlaps with the other two tools, which could cause some confusion about when to use it versus separate calls.
All tool names follow a consistent snake_case pattern with a 'websearch_' prefix and descriptive verb_noun combinations (e.g., fetch_page, search, search_and_fetch). This makes the set predictable and easy to understand.
With 3 tools, this server is well-scoped for web search functionality. Each tool serves a clear purpose: searching, fetching, and a combined operation. This count is appropriate and avoids unnecessary complexity.
The toolset covers core web search operations effectively: searching, fetching content, and a combined workflow. A minor gap is the lack of advanced search features like filtering or pagination, but agents can work around this with the provided tools.