Spicrawl

Submit a batch scrape job

spicrawl_batch_submit

Submit many URLs to be scraped as one asynchronous job, with shared settings applied to every URL. Give EITHER urls or items, not both (at least one URL, unless open is true). Returns the job object (id, status, estimated_credits, progress). Poll with spicrawl_batch_status, read with spicrawl_batch_results or spicrawl_batch_task_content. Use this instead of many spicrawl_scrape calls when you have tens or thousands of URLs. Set open: true to keep the job accepting more URLs via spicrawl_batch_add_items; an open job never finishes until you call spicrawl_batch_close.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	A human label for the job.
`open`	No	Keep the job accepting items after submission (append with spicrawl_batch_add_items, finish with spicrawl_batch_close).
`urls`	No	Shorthand: URLs scraped with the shared settings and no per-item overrides. Mutually exclusive with `items`.
`wait`	No	Milliseconds to wait after load (rendered scrapes).
`items`	No	Long form: one /v1/scrape request object per item. Besides `url` and `external_id`, any /v1/scrape field (e.g. `js_render`, `wait_for`, `response_format`) overrides the shared setting for that item only. Mutually exclusive with `urls`.
`engine`	No	Pin the scrape engine for every item: `fetch` or `obscura` (must be allowed by the plan and served by the deployment); `camoufox` is coming soon, do not pin it yet. `chromium` cannot be pinned in a batch — use `render: true`, or spicrawl_scrape.
`format`	No	Output format for every item (`response_format`). spicrawl_batch_submit defaults to 'markdown', the same as spicrawl_scrape; an item's own `response_format` overrides it.
`render`	No	Render every URL with a browser (`js_render`).
`max_cost`	No	Ceiling in credits for ONE item (not the whole job — see credit_budget).
`priority`	No	Scheduling priority of the job relative to your other jobs.
`wait_for`	No	CSS selector to wait for before capturing (rendered scrapes).
`concurrency`	No	Max items in flight at once for this job (may be capped by the server; see warnings).
`max_attempts`	No	Per-item retry attempts on failure.
`credit_budget`	No	Ceiling on the WHOLE job, in credits; the run aborts when it would exceed this.
`premium_proxy`	No	Coming soon: not available yet, do not send. Use residential managed-pool exits for every URL.
`proxy_country`	No	Coming soon: not available yet, do not send. ISO-3166 alpha-2 exit country; requires premium_proxy.
`custom_headers`	No	Extra request headers sent with every URL.
`block_resources`	No	Resource types to block while rendering, e.g. ["image","font","media"].
`failure_threshold`	No	Abort the job once this many items have failed.
`main_content_only`	No	Strip each page to its main article.
`webhook_endpoint_id`	No	Id of a registered webhook endpoint notified (with the job object) when the job completes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare non-destructive, non-idempotent, open-world behavior, and the description adds crucial async lifecycle detail beyond them: returns a job object with specific fields, requires polling, open jobs never finish until closed, and shared settings apply to every URL. This operational model is not in the annotations. Auth/rate-limit notes are absent but not critical here.

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?

Front-loaded with the purpose, followed by constraints, return behavior, workflow routing, and the open/close pattern. Every sentence contributes and no filler is present. Appropriate density for a 21-parameter asynchronous tool.

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

Completeness5/5

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

Given 21 params, nested items, no output schema, and a complex async workflow, the description covers submission rules, return shape, polling, result retrieval, and open/close lifecycle. Nothing essential for correct invocation is missing; per-parameter details are handled by the schema.

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% for 21 parameters, so the schema already documents all parameter meanings; baseline 3 applies. The description adds only the conditional 'at least one URL unless open is true' and repeats the urls/items mutual exclusivity already present in schema descriptions. Marginal additional value over structured fields.

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?

States a specific verb (Submit) and resource (batch scrape job) with scope (many URLs, one asynchronous job, shared settings). Explicitly distinguishes from siblings by naming spicrawl_batch_status, spicrawl_batch_results, spicrawl_batch_task_content, and spicrawl_scrape. An agent can route correctly without opening schemas.

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?

Explicitly says to use this instead of many spicrawl_scrape calls when you have tens or thousands of URLs, and points to status/results/task_content for follow-up. Also explains the open:true workflow with spicrawl_batch_add_items and spicrawl_batch_close. No ambiguity about when to choose this tool vs alternatives.

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

All Spicrawl tools Inspect

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

Need Help?