mcp-webextrator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACEDATACLOUD_API_TOKEN | Yes | Your AceDataCloud API token |
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 |
|---|---|
| webextrator_extractA | Extract structured content from a web page using the WebExtrator API. |
| webextrator_renderA | Render a web page and return the fully rendered HTML. |
| webextrator_get_usage_guideA | Get a comprehensive guide for using the WebExtrator tools. |
| webextrator_get_taskA | Retrieve the result of a single previously created extract or render task. |
| webextrator_get_tasks_batchA | Retrieve the results of multiple previously created extract or render tasks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| webextrator_guide | Guide for choosing the right WebExtrator tool for web extraction and rendering tasks. |
| webextrator_workflow_examples | Common workflow examples for WebExtrator tasks. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Extract and render both involve fetching a URL, but their output types are clearly differentiated: structured content vs. raw rendered HTML. Get_task and get_tasks_batch are likewise distinct by single vs. batch retrieval, with descriptions that reinforce when each should be used.
All tools follow the same webextrator_verb_noun pattern with consistently descriptive verbs: extract, render, get_usage_guide, get_task, get_tasks_batch. The naming is uniform, predictable, and easy to navigate.
Five tools is a well-scoped set for a web extraction server: two core operations, two async retrieval methods, and a usage guide. Each tool serves a clear purpose without unnecessary bloat.
The tool surface covers the full lifecycle: submit extract/render tasks, poll a single task, and retrieve tasks in batch. The usage guide fills discoverability gaps, and the async=true path is well integrated with task retrieval, leaving no obvious dead ends.