Skip to main content
Glama
ReftrixMCP
by TKMD

page.batch_analyze

Batch analyze up to 50 URLs in parallel by submitting async jobs and returning a batch ID to poll for results.

Instructions

Batch analyze multiple URLs in parallel. Submits all URLs as async BullMQ jobs and returns immediately with a batch ID.

Features:

  • Up to 50 URLs per batch

  • Configurable concurrency (1-5, default: 3)

  • SSRF validation for all URLs before submission

  • Graceful degradation: individual failures don't affect the batch

  • Progress tracking via page.getJobStatus(batch_id)

  • Rate limiting within analysis tier (10 RPM)

Use page.getJobStatus with batch_id to poll for results.

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": "page.batch_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesTarget URLs to analyze (1-50)
timeoutNoBatch-level timeout in ms (default: 1800000 = 30min)
featuresNoShared analysis features (default: all enabled)
on_errorNoBehavior on individual job failure: 'skip' (continue) or 'abort' (stop batch)
concurrencyNoParallel jobs within batch (1-5, default: 3)
layoutOptionsNoShared layout options for all URLs
respect_robots_txtNoRespect robots.txt (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses async/non-blocking behavior, the 50-URL cap, concurrency bounds, SSRF pre-validation, per-URL failure isolation, and a 10 RPM tier rate limit. These are exactly the operational facts an agent needs to avoid mis-calling an async batch tool.

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

Conciseness4/5

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

The lead sentence front-loads the core behavior and the bullets are scannable. There is mild redundancy: progress tracking via page.getJobStatus appears both as a bullet and as a closing sentence, and 'BullMQ' is an implementation detail that does not help tool selection.

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 7-parameter tool with nested objects and no output schema, the description covers the important contract: it returns immediately with a batch ID and results are retrieved via page.getJobStatus. It does not describe what the polled result payload contains or whether partial results are visible mid-batch, which is the main remaining gap.

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%, so every parameter is already documented, and the description mostly restates schema facts (concurrency 1-5 default 3, 50-URL cap). It does add a little meaning by tying 'graceful degradation' to the on_error='skip' behavior and by noting SSRF validation applies to the urls array, but timeout, features, and layoutOptions get no added explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource with scope: batch-analyze multiple URLs in parallel, submitted as async jobs, returning a batch ID immediately. That clearly separates it from the single-URL sibling page.analyze, though it never names page.analyze as the alternative, so the differentiation is inferred rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage path: submit up to 50 URLs, then poll page.getJobStatus with the returned batch_id for results. What is missing is an explicit exclusion rule such as 'for a single URL use page.analyze instead', which would make routing unambiguous among 27 siblings.

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