Skip to main content
Glama
Sign In
web-scraper-server

web-scraper-server

by ImYourBoyRoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

batch_contacts

Extract contacts from multiple URLs concurrently. Uses CPU-aware parallelism to balance speed and resource usage.

Instructions

Extract contacts from multiple URLs in parallel.

Uses hardware-limited concurrency (CPU cores - 1) for optimal performance.

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": "batch_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
timeout_profileNoresearch

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.5

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 full burden. It discloses a meaningful behavioral trait (hardware-limited concurrency), but omits error handling, rate limits, and whether the operation is synchronous or returns a job, leaving significant unknowns.

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?

The description is two sentences, front-loaded with purpose, and contains no filler. Every word contributes meaning.

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

Completeness3/5

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

An output schema exists, which may cover return values, but the description lacks constraints like URL limits, asynchronous behavior, or prerequisites. Given the batch processing nature and sibling tools like poll_job, failing to mention job semantics is a gap.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only clarifies that urls is a list of URLs, while timeout_profile remains completely unexplained, including its meaning and acceptable values.

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?

The description clearly states the tool extracts contacts from multiple URLs in parallel, using a specific verb and resource. This distinguishes it from single-URL extract_contacts and more general batch_scrape.

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

Usage Guidelines3/5

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

The phrase 'multiple URLs in parallel' implies a batch use case, but no explicit guidance is given about when to choose this over alternatives like extract_contacts or batch_scrape. No exclusion criteria or alternative tools are mentioned.

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