Skip to main content
Glama
Sign In
alterlab-mcp-server

alterlab-mcp-server

by RapierCraft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

alterlab_batch_scrape

Scrape 2-20 URLs in parallel in one synchronous call, returning all results without polling. Use it when fetches hit 403/429, CAPTCHA, bot challenges, or empty JavaScript shells.

Instructions

Scrape 2-20 URLs in parallel and get every result back in one synchronous call, no polling required. Use when a normal fetch returns 403/429, a bot-protection challenge page, a CAPTCHA, or an empty JavaScript shell. Failed URLs report their error; successful ones return content. For 20+ URLs use alterlab_batch.

Input Schema

NameRequiredDescriptionDefault
urlsYesList of URLs to scrape (max 20). All results are returned synchronously.
formatsNoOutput formats applied to every URL. 'markdown' is best for LLM consumption.
timeoutNoRequest timeout in seconds per URL (1-300).
render_jsNoRender JavaScript using headless browser for all URLs. Required for JS-heavy sites. Forces tier 4 ($0.004/req).
use_proxyNoRoute all requests through premium proxy (+$0.0002/req).
max_concurrentNoMaximum number of URLs to scrape in parallel (1-10, default 3). Higher values finish faster but consume more concurrent connections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.9.0
    • changedInput schema / properties / formats / items / enum
      Previous value: -[
-  "text",
-  "json",
-  "json_v2",
-  "html",
-  "markdown",
-  "rag",
-  "content"
-]New value: +[
+  "text",
+  "json",
+  "json_v2",
+  "html",
+  "markdown",
+  "rag",
+  "content",
+  "raw"
+]
    • changedInput schema / properties / render_js / description
      Previous value: -"Render JavaScript using headless browser for all URLs. Required for JS-heavy sites. Increases cost to tier 4 (~$0.001/req)."New value: +"Render JavaScript using headless browser for all URLs. Required for JS-heavy sites. Forces tier 4 ($0.004/req)."
    • addedInput schema / properties / urls / items / maxLength
      Added value: +2083
    • changedInput schema / properties / use_proxy / description
      Previous value: -"Route all requests through premium proxy (+~$0.0002/req)."New value: +"Route all requests through premium proxy (+$0.0002/req)."
  2. Addedv1.8.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry behavior, and it does disclose the key traits: fully synchronous execution with no polling, and per-URL error containment so one failure does not abort the batch. It omits auth requirements, rate limits, and cost behavior beyond what the schema already states.

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?

Four short sentences, front-loaded with the core capability, then trigger conditions, then return semantics, then the escape hatch to the sibling. No filler sentences.

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

Completeness4/5

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

For a 6-parameter tool with no annotations and no output schema, the description covers execution model, failure handling, and tool selection adequately. It could say more about the shape of the aggregated response (e.g. result ordering or whether errors are inline per URL), which matters for a batch call.

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

Parameters3/5

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

Schema description coverage is 100% and the parameters are self-documenting, so baseline is 3. The description reinforces parallelism but does not explain formats, timeout, or proxy trade-offs beyond the schema, and its '2-20 URLs' range slightly conflicts with the schema's minItems of 1.

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?

States a specific verb and resource (scrape URLs) plus the defining scope: parallel, synchronous, 2-20 URLs, no polling. It differentiates itself from the sibling alterlab_batch by count threshold, so an agent can route without opening either schema.

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?

Gives explicit when-to-use triggers (403/429, bot-protection challenge, CAPTCHA, empty JS shell) and names the alternative for the out-of-scope case (20+ URLs → alterlab_batch). Both the selection condition and the exclusion are stated.

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

Deploy Server

Other Tools