No user-submitted related servers found.
Scored across 26 tools
Tools are grouped into distinct domains (scrape/extract, crawl, batch, sessions, account, beta) and descriptions explicitly cross-reference siblings to steer selection. However, a few pairs blur boundaries: alterlab_batch vs alterlab_batch_scrape (async vs inline), alterlab_update_session vs alterlab_refresh_session (both rotate cookies), and alterlab_get_usage vs alterlab_check_balance all require reading the descriptions to disambiguate. These overlaps are documented but still create mild misselection risk.
Every tool uses the alterlab_ prefix with snake_case, and the vast majority follow a clear verb_noun pattern (create_session, delete_session, list_sessions, estimate_cost, enable_beta_feature). The few deviations (crawl_status, batch_status, bare verbs like search/map) are natural and remain fully predictable and readable.
At 26 tools the surface is on the heavy side and pushes past the comfortable range. Several tools could be consolidated (batch vs batch_scrape, list_beta_features vs list_my_beta_features), though the breadth of the platform's features (scraping, crawling, batching, sessions, account, beta flags) partially justifies the count.
Coverage is strong: full session lifecycle (create/read/update/refresh/validate/delete), scrape/crawl/batch with status and cancel, async job polling, cost estimation, and balance/usage. Minor gaps remain, such as no dedicated tool for managing completion webhooks or exports, both of which are only exposed as parameters.