MCP Web Research 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_googleC | Search Google for a query |
| visit_pageC | Visit a webpage and extract its content |
| take_screenshotB | Take a screenshot of the current page |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| agentic-research | Conduct iterative web research on a topic, exploring it thoroughly through multiple steps while maintaining a dialogue with the user |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: search_google finds web pages, visit_page loads and extracts content from a specific URL, and take_screenshot captures visual data from the current page. An agent can easily differentiate these functions without confusion.
All tool names follow a consistent verb_noun pattern using snake_case: search_google, take_screenshot, and visit_page. This uniformity makes the set predictable and easy to understand at a glance.
With only 3 tools, the server feels thin for a 'Web Research Server' scope, as it lacks operations like navigating pages, interacting with elements, or managing browser sessions. While the tools cover basic functions, the count is borderline low for comprehensive web research tasks.
There are significant gaps in the tool surface for web research: no navigation tools (e.g., go_back, click_element), no interaction capabilities (e.g., fill_form, scroll), and no session management. This incomplete coverage will likely cause agent failures in complex research workflows.