Scored across 12 tools
Each tool has a clearly distinct purpose: fetching raw HTML, extracting declared data, converting to markdown, testing selectors, compiling/replaying/healing extractors, auditing structured data, reading feeds, mapping sites, crawling, and batch extraction. Even overlapping tools like extract_declared and extract_many are separated by single vs. multiple pages, and crawl_site vs. map_site by following links vs. listing sitemap URLs. No two tools appear to do the same thing.
Most tools follow a verb_noun pattern (fetch_page, compile_extractor, run_extractor, audit_page, read_feed, map_site, crawl_site, select_values), but a few deviate: 'extract_declared' and 'extract_many' use verb+modifier, and 'page_markdown' is noun-like, breaking the pattern. Still, the naming is generally predictable and readable.
12 tools is well within the typical 3-15 range for a web data extraction server. Each tool addresses a distinct capability—fetching, extracting, testing, learning, replaying, healing, auditing, reading feeds, mapping, crawling, and batch processing—without redundancy or bloat.
The toolset covers the full lifecycle of web data extraction: raw fetch, structured data extraction, markdown conversion, selector testing, extractor creation/replay/healing, structured data auditing, feed reading, sitemap mapping, site crawling, and batched extraction. It also handles TDM rights, Wayback Machine, and pagination, leaving no obvious gaps for its stated purpose.