Skip to main content
Glama
spidra-io

spidra-mcp-server

Official
by spidra-io

spidra_scrape

Read-only

Extract and compare content from up to three known URLs using AI. Returns a single combined answer with raw page markdown, ideal for summarizing or comparing related pages.

Instructions

Scrape 1-3 known URLs and extract their content with AI. This tool WAITS for the result (typically 10-60 seconds) and returns the extracted content directly.

IMPORTANT: with multiple URLs, their content is COMBINED and the AI produces ONE answer across all of them (the per-URL raw pages are still returned in "pages"). Use several URLs here when you want to compare or synthesize across pages — e.g. "compare the pricing on these two pages". If instead you want the SAME extraction run separately on each URL (own result per URL), use spidra_batch_scrape even for just 2 URLs.

Best for: one URL, or one combined answer drawn from 2-3 related URLs. Not for: per-URL independent results (use spidra_batch_scrape) or discovering pages on a site (use spidra_crawl).

Behavior notes:

  • Omit "prompt" and "schema" to get the raw page content as markdown.

  • Pass "prompt" for free-form AI extraction, and add "schema" when you need a guaranteed JSON shape. Define every field in the schema — untyped objects come back empty.

  • Use "actions" to interact with the page first (dismiss cookie banners, type into search boxes, scroll, or loop over elements with forEach).

  • Use "useProxy" with "proxyCountry" for geo-restricted or bot-protected sites.

  • Costs: 2 credits per URL plus AI tokens; CAPTCHA solves cost 10 credits each.

Usage example:

{
  "name": "spidra_scrape",
  "arguments": {
    "urls": ["https://example.com/pricing"],
    "prompt": "Extract all pricing plans with name, price, and included features",
    "output": "json"
  }
}

Returns: extracted content plus token/credit stats. If the wait window is exceeded, the job keeps running — poll spidra_check_scrape_status with the returned jobId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYes1-3 URLs to scrape in parallel
outputNoOutput format (default "markdown")
promptNoWhat to extract, in plain English. Omit for raw markdown.
schemaNoJSON Schema enforcing the exact output shape. Define EVERY field you want extracted — an untyped object with no properties comes back empty. Missing fields return null instead of hallucinated values.
actionsNoBrowser actions to run on each URL before extraction, in order
cookiesNoRaw Cookie header string for pages behind a login, e.g. "session=abc"
useProxyNoRoute through a residential proxy (for blocked/geo-restricted sites)
scrapeModeNo"fast" = HTTP only (no browser), cheaper but less capable
screenshotNoCapture a viewport screenshot (URL returned)
proxyCountryNoTwo-letter country code for the proxy, e.g. "us", "de", "jp", or "eu"/"global"
extractContentOnlyNoStrip navigation/ads/boilerplate before extraction
Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses the synchronous wait behavior, timeout fallback with spidra_check_scrape_status, credit costs, CAPTCHA costs, and the combined-answer behavior. No contradiction with annotations; it adds substantial context.

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 description is fairly long but well-structured with headers and bullets. A few points restate schema descriptions (e.g., untyped schema warning), but the example and prioritization earn their place. Slightly tighter would be perfect.

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?

With no output schema, the description explains returns (content + stats) and timeout behavior. It covers costs, alternatives, usage example, and edge cases like CAPTCHA and proxy. This is a complete guide for agent invocation.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds essential meaning: omitting prompt/schema yields raw markdown, untyped objects come back empty, and the relationship between prompt and schema is clarified. The usage example demonstrates correct argument structure.

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 opens with a specific verb+resource: "Scrape 1-3 known URLs and extract their content with AI." It clearly distinguishes from siblings by explaining that multiple URLs produce a combined answer, while independent per-URL extraction belongs to spidra_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 Guidelines5/5

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

Explicit "Best for" and "Not for" sections name alternatives (spidra_batch_scrape, spidra_crawl). It also gives conditional guidance for actions, proxy, and schema usage, telling the agent when each parameter is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/spidra-io/spidra-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server