Skip to main content
Glama
n24q02m

WET - Web Extended Toolkit

by n24q02m

extract

Read-only

Retrieve clean, readable content from web pages or local files by providing URLs or file paths. Convert HTML, PDF, DOCX, PPTX, or XLSX into Markdown format for easy analysis.

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"}])

  • diff: Track content changes across fetches of the same URL(s). Example: extract(action="diff", urls=["https://example.com/pricing"])

Key parameters:

  • urls (required for extract/batch/crawl/map/extract_structured/diff): 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

  • refetch (diff): Fetch a fresh copy before comparing (default: true). Set false to compare already-recorded snapshots without a new network fetch.

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

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint, but the description adds substantial behavioral context: batch per-domain rate limiting (max 50 URLs), crawl depth and max_pages constraints, stealth anti-bot bypass, persistent browser sessions, refetch behavior, and the ability to click/fill/submit via interact. This goes well beyond the annotations and sets accurate expectations.

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

Conciseness5/5

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

The description is long but well-structured: opening purpose, actionable examples for each of nine modes, and a key-parameters section. It front-loads the core use case and search distinction. Every sentence earns its place given the tool's complexity; the final pointer to 'help' is a minor but useful note.

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?

For an 18-parameter, multi-action tool, the description is remarkably complete. It documents every action mode with examples, covers nearly all parameters with defaults and constraints, and notes the existence of an output schema. No critical gaps remain for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description carries the full burden. It compensates with action-specific mappings, defaults (max_urls=5, depth=2, token_budget=10000), constraints (max crawl depth 5, max_pages 100), and concrete examples showing how to pass parameters. Only 'prompt' is not explicitly described, but overall semantics are richly defined.

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' and enumerates nine specific action modes (extract, batch, crawl, map, convert, extract_structured, agent, interact, diff). It distinguishes itself from the sibling 'search' tool by explicitly 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?

Provides explicit when-to-use guidance: 'Use this when you have a specific URL and need its content.' It names the alternative search tool, and each action includes an example with concrete parameter usage. The key parameters section further clarifies which parameters apply to which 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/n24q02m/wet-mcp'

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