web-retrieval-mcp
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 |
|---|---|
| analyze_web_structureB | 深度解析指定URL网页的前端设计架构与后端交互面（仅需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 1 tool
With only one tool, there is no ambiguity or overlap; the agent can only select that tool.
The single tool name 'analyze_web_structure' follows a clear verb_noun pattern, consistent with good naming conventions.
A single tool for a 'web-retrieval-mcp' server feels too limited; typically web retrieval involves multiple operations like fetching, parsing, or searching, making one tool insufficient for meaningful coverage.
The tool only analyzes web structure, omitting essential retrieval actions such as fetching raw content, extracting text, or handling different content types, leaving significant gaps for the stated domain.