Enhanced Web Scraper 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_elementC | Inspect a DOM element by selector and return its attributes, text, and computed styles |
| scrape_pageC | Scrape content from any web page (regular websites, React apps, or React Native web apps) using Playwright |
| inspect_react_appC | Inspect React Native web app with component tree, props, and state analysis |
| wait_for_react_stateB | Wait for React component state changes, data loading, or navigation |
| execute_in_react_contextC | Execute JavaScript in React context to inspect components, state, or trigger actions |
| check_expo_dev_serverC | Check if Expo development server is running and get app status |
| test_react_appC | Test any React app (regular React or React Native web) with enhanced interactions and mobile gestures |
| get_page_infoC | Get comprehensive information about a web page (title, meta tags, performance metrics) |
| test_dropdown_with_error_captureC | Test dropdown interactions with comprehensive console error capture and page state monitoring |
| wait_for_elementB | Wait for an element to appear on the page (useful for dynamic React content) |
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 10 tools
The tools have some clear distinctions, such as between scraping, inspecting, and testing functions, but there is significant overlap and ambiguity. For example, 'inspect_element' and 'inspect_react_app' both involve inspection, and 'execute_in_react_context' could be confused with 'test_react_app' or 'wait_for_react_state', making tool selection potentially confusing for an agent.
The naming follows a mostly readable verb_noun pattern, but there are inconsistencies in verb usage and specificity. Tools like 'scrape_page' and 'get_page_info' use different verbs for similar actions, and 'test_dropdown_with_error_capture' includes additional descriptors, deviating from the simpler naming of others like 'wait_for_element'.
With 10 tools, the count is reasonable for a web scraper server that covers scraping, inspection, testing, and waiting functions. It's well-scoped for the domain, though it might be slightly heavy, as some tools could be consolidated to reduce overlap without losing functionality.
The tool set covers core web scraping and testing workflows, including page scraping, element inspection, React app analysis, and interaction testing. Minor gaps exist, such as the lack of tools for handling authentication or advanced data extraction, but agents can likely work around these with the provided tools for most common tasks.