Skip to main content
Glama

Run multiple URLs in parallel

browser_swarm

Opens multiple URLs concurrently in a pooled set of worker tabs and returns one merged Markdown report, letting each task use a query to scope extracted content.

Instructions

Open several URLs concurrently across a pool of up to 3 recycled worker tabs (max 2 per domain) and return one merged Markdown report. Use this instead of sequential navigations when a task spans multiple pages, lists or links. Each task can carry a "query" to scope the extracted content.

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": {
      "tasks": "<tasks>"
    },
    "name": "browser_swarm"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYesTasks to run concurrently.
isolatedNoRun each task in a throwaway context cloned from the current storage state. Use for authenticated or mutating workflows so changes never leak back into the main session.
maxCharsPerTaskNoCharacter budget per task. Default: 6000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does reveal concurrency limits (3 worker tabs, 2 per domain), the merged Markdown output, and that query scoping is available. It stays silent on important behavioral traits for a parallel tool: what happens when one task fails, whether results appear in task order, and how labels structure the merged report.

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?

Three tight sentences with the core mechanism front-loaded ahead of the usage rule and the parameter note; nothing is padding. The final sentence on 'query' is mildly redundant with the schema's own parameter description, which keeps it from being maximally efficient.

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?

There is no output schema, and the description compensates by stating the return is one merged Markdown report. Combined with the concurrency limits and usage rule, an agent has nearly enough to call it correctly; only failure/partial-result semantics remain uncovered.

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 the schema already explains url, label, query, isolated, and maxCharsPerTask, making 3 the baseline. The description restates the query parameter's scoping role but says nothing about the isolated flag or the character budget, so it adds essentially no meaning beyond the schema.

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 names a concrete verb and resource ('Open several URLs concurrently') and quantifies the mechanism: a pool of up to 3 recycled worker tabs, max 2 per domain, merged into one Markdown report. It clearly describes what the tool does but never names a sibling, and a closely related tool like browser_batch is not distinguished, leaving a small ambiguity an agent must resolve from names alone.

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 an explicit selection rule: 'Use this instead of sequential navigations when a task spans multiple pages, lists or links.' That tells the agent the condition for choosing this tool over repeated single navigations, though it frames the alternative generically rather than naming a specific sibling or giving a when-not-to-use case.

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