Skip to main content
Glama
Sign In
dawg-mcp

dawg-mcp

by dawgswarm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

scrape_batch

Scrape multiple URLs in a batch process, receiving a job ID to track progress.

Instructions

Start a batch scrape over many URLs. Returns immediately with a job_id.

Poll progress with scrape_job_status(job_id).

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

Input Schema

NameRequiredDescriptionDefault
urlsYes
formatNomarkdown
concurrencyNo
main_contentNo
timeout_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions async behavior (returns immediately with job_id) but lacks details on side effects, permissions, limits, or cancellability. It does not describe what happens to the URLs or error handling.

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 extremely concise with two sentences. It front-loads the purpose and action, with no unnecessary words.

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

Completeness2/5

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

Given 5 parameters and async behavior, the description is too minimal. It omits parameter explanations, output details (job_id type), error handling, and how batch differs from crawl. Incomplete for a tool of this complexity.

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

Parameters1/5

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

Schema coverage is 0%, so the description should compensate. It does not explain any parameter: format options, concurrency meaning, main_content, timeout_ms. Only 'many URLs' vaguely references the urls parameter.

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 verb 'Start', the resource 'batch scrape', and the scope 'over many URLs'. It distinguishes from siblings like scrape_page (single page) and scrape_crawl (crawl). The return of a job_id and polling instruction are also clear.

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?

The description explains the immediate return of job_id and directs the user to poll with scrape_job_status. It implies usage for batch jobs, but does not explicitly say when not to use it or compare to alternatives.

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