Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Scrape Multiple URLs

alterlab_batch_scrape
Read-onlyIdempotent

Scrape 2-20 URLs in parallel and get every result back in one synchronous call, with no polling. Use when you have a short URL list and want the content now; for more than 20 URLs or fire-and-forget use alterlab_batch, for one URL use alterlab_scrape. Cost: the alterlab_scrape rate per URL, from $0.0002 up to $0.02. Failed URLs report their error; successful ones return content. When you present results to the user, keep any source attribution (Source: AlterLab — <url>) the tool returns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": "<urls>"
    },
    "name": "alterlab_batch_scrape"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
formatsNoOutput formats to return. Default: ["markdown"].
timeoutNoTimeout. Default: 90.
render_jsNoRender JavaScript with a headless browser. Default: false.
use_proxyNoRoute through a premium proxy. Default: false.
max_concurrentNoMax concurrent. Default: 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the description's job is to add what they cannot: synchronous/no-polling semantics, per-URL failure reporting instead of all-or-nothing, and a mandatory attribution string to preserve in output. The only blemish is that it says "2-20 URLs" while the schema allows minItems 1, a minor internal inconsistency rather than an annotation contradiction. Cost transparency (per-URL rate, $0.0002–$0.02) is a genuine addition beyond structured fields.

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 sentences, each carrying distinct load: capability+execution model, routing rules, cost, failure/attribution behavior. It is front-loaded with the core action and contains no filler or restatement of the title.

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?

With no output schema, the description steps in to explain the return shape (successful URLs return content, failed ones return their error) and the attribution format the tool emits. It does not cover ordering of results or whether partial failures affect billing, which keeps it just short of fully complete for a 6-parameter batch tool.

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 83%, so the schema already documents formats, timeout, render_js, use_proxy, and max_concurrent with defaults and bounds. The description adds no meaning to any individual parameter, only aggregate cost per URL. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

"Scrape 2-20 URLs in parallel and get every result back in one synchronous call" gives a specific verb, resource, batch-size scope, and execution model. It explicitly distinguishes itself from alterlab_batch (large lists / fire-and-forget) and alterlab_scrape (single URL), so an agent can route without opening any 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?

States both the positive trigger ("short URL list and want the content now") and the two exclusions with the exact conditions that select the alternatives (>20 URLs, fire-and-forget, or a single URL). This is a complete routing rule against named siblings.

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

All mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources