Skip to main content
Glama
expandingideas-ai

WET - Web Extended Toolkit MCP Server

extract

Read-only

Extract clean content from URLs, batch process multiple pages, crawl sites, convert local documents, or perform multi-step research with an agent.

Instructions

Read and return full page content from URLs or local files. Use this when you have a specific URL and need its content. For finding URLs first, use the search tool instead.

Actions:

  • extract: Get clean content from URLs. Example: extract(action="extract", urls=["https://example.com/article"])

  • batch: Batch extract with per-domain rate limiting (max 50 URLs). Example: extract(action="batch", urls=["https://a.com/1", "https://b.com/2"])

  • crawl: Deep crawl following links from root URLs. Example: extract(action="crawl", urls=["https://docs.example.com"], depth=2)

  • map: Discover site URL structure without extracting content. Example: extract(action="map", urls=["https://example.com"])

  • convert: Convert local files (PDF, DOCX, PPTX, XLSX) to Markdown. Example: extract(action="convert", paths=["/home/user/report.pdf"])

  • extract_structured: Extract structured data using JSON Schema + LLM. Example: extract(action="extract_structured", urls=["https://example.com/pricing"], schema={"type": "object", "properties": {"price": {"type": "string"}}})

  • agent: Multi-step research orchestration -- search the web, extract top results, synthesize a cited Markdown answer. Example: extract(action="agent", query="latest pydantic 2 changes", max_urls=5)

  • interact: Drive a page with click/fill/submit via patchright. Example: extract(action="interact", url="https://example.com/login", actions=[{"type": "fill", "selector": "#email", "value": "x@y.com"}, {"type": "submit", "selector": "form"}])

Key parameters:

  • urls (required for extract/batch/crawl/map/extract_structured): List of URLs

  • paths (required for convert): List of local file paths

  • query (required for agent): Research question to answer

  • url (required for interact): Page URL to drive

  • actions (required for interact): List of {type, selector?, description?, value?} ops

  • max_urls (agent): Default 5, hard cap 20

  • synthesis_model (agent): Override LLM model for the synthesis step

  • token_budget (agent): Max prompt tokens (default 10000)

  • session (interact): Persistent session id; reuses browser across calls

  • screenshot (interact): Capture post-interaction screenshot

  • format: Output format -- "markdown" (default), "text", "html"

  • depth: Crawl depth (default: 2, max: 5)

  • max_pages: Max pages for crawl/map (default: 20, max: 100)

  • stealth: Enable anti-bot bypass for protected sites (default: false)

  • schema: JSON Schema dict for extract_structured

Use help tool with tool_name="extract" for full parameter documentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
urlsNo
pathsNo
depthNo
max_pagesNo
formatNomarkdown
stealthNo
schemaNo
promptNo
queryNo
max_urlsNo
synthesis_modelNo
token_budgetNo
actionsNo
sessionNo
screenshotNo
urlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint and openWorldHint. The description adds extensive behavioral context: it explains rate limiting for batch, stealth mode for bot bypass, default and max values for depth and max_pages, conversion of local files, structured extraction with LLM, multi-step research (agent), and page interaction (interact). No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured with sections: overall purpose, list of actions with examples, key parameters, and a note to use help. It is front-loaded with the core purpose. Every sentence is informative, though some details could be condensed. Given the tool's complexity, the length is justified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (17 parameters, 8 actions), the description is fairly complete. It covers all actions, key parameters, defaults, and constraints. Since there is an output schema, it does not need to describe return values in detail. It also addresses the openWorldHint by explaining that responses can vary (e.g., depending on URL content).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries full burden. It lists 'Key parameters' and explains which parameters are required for each action (e.g., urls for extract, paths for convert). It also describes the format for interact actions and defaults for many parameters. However, a few parameters like 'prompt' are not detailed, and not every parameter is explicitly mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Read and return full page content from URLs or local files', specifying the verb and resource. It also distinguishes from the sibling 'search' tool by saying 'For finding URLs first, use the `search` tool instead.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: 'Use this when you have a specific URL and need its content.' It also contrasts with the `search` tool for finding URLs. Additionally, it breaks down multiple actions (extract, batch, crawl, etc.) with examples, helping the agent choose the right action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/expandingideas-ai/mcp-wet'

If you have feedback or need assistance with the MCP directory API, please join our Discord server