web-data-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token for authentication | |
| WEB_DATA_MCP_HTTP_TOKEN | No | Optional token for HTTP transport authentication |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_urlA | Scrape a public web page into clean markdown in one call: runs a crawler, waits, scores the result (completeness, bot-wall detection), and automatically retries with stronger settings when quality is low. Costs Apify credits per run. For arbitrary actors or fire-and-forget runs use run_actor instead. |
| run_actorA | Start an allowlisted Apify actor with an explicit input object. Returns run_id and dataset_id handles for get_run_status / fetch_dataset_items / validate_dataset. Costs Apify credits. Prefer scrape_url for simple page scrapes. |
| get_run_statusA | Check whether an actor run has finished and where its dataset is. Free and safe to poll. |
| fetch_dataset_itemsA | Read items from an actor run dataset with pagination, field projection, and a hard token budget. Start with response_format "summary" to see the shape cheaply, then fetch "items" with a fields projection. Items arrive as JSON in the text content; structured content carries pagination metadata (total, next_offset, truncated). |
| validate_datasetA | Score a dataset before trusting it: schema pass rate (if a JSON Schema is given), field completeness, duplicate rate, and bot-wall detection. Use the score to decide between consuming the data and retry_low_quality_run. |
| retry_low_quality_runA | Re-run an actor with progressively stronger anti-blocking settings (residential proxies, then a browser crawler) until the dataset quality score reaches the threshold or attempts are exhausted. Each attempt costs Apify credits. |
| dataset_to_rag_documentsA | Turn scraped items into embedding-ready documents: token-bounded chunks with overlap, source attribution, stable content-hash ids for idempotent vector upserts, and selected metadata. Paginate with offset/limit for large datasets. |
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 7 tools
Each tool has a clearly distinct role: run management, scraping, actor execution, data retrieval, quality validation, retry logic, and RAG conversion. Overlapping tools like scrape_url and run_actor are explicitly differentiated in their descriptions, so an agent can reliably select the correct one.
Most tools follow a consistent verb_noun snake_case pattern (get_run_status, scrape_url, run_actor, fetch_dataset_items, validate_dataset, retry_low_quality_run). The exception is dataset_to_rag_documents, which lacks a leading verb and breaks the pattern, though it remains readable and unambiguous.
Seven tools is a well-scoped count for a web data extraction and processing server. Each tool addresses a distinct step in the pipeline without redundancy, making the set feel complete yet not overwhelming.
The tool surface covers the full lifecycle: initiating extractions (scrape_url/run_actor), monitoring runs (get_run_status), fetching results (fetch_dataset_items), validating quality (validate_dataset), improving results (retry_low_quality_run), and preparing output for downstream use (dataset_to_rag_documents). No critical gaps are apparent for the stated purpose.