Skip to main content
Glama
Sign In
Scrapi MCP Server

Scrapi MCP Server

by bamchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

scrape_urls

Scrape multiple URLs in parallel to get clean Markdown content, even from blocked sites, for AI analysis.

Instructions

Scrapes multiple webpages in parallel and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.

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_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesURLs to scrape (max 10)
formatNoOutput format: markdown (default) or textmarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A3.8/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 burden. It discloses parallel processing and browser rendering for blocked sites, which are useful behavioral traits. However, it omits potential limitations such as rate limits, errors on inaccessible pages, or the size of returned content, leaving some operational expectations unspecified.

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?

Two efficient sentences with zero filler. The first sentence front-loads the action and purpose, while the second adds a distinctive capability. Every word contributes value.

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?

For a relatively simple tool with fully described parameters, the description adequately explains the tool's purpose, output format, and unique ability to handle blocked sites. It lacks only an explicit tie-in to the sibling tool 'scrape_url' and more detail on failure behavior, but these are minor gaps given the simplicity.

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 coverage is 100%; both 'urls' and 'format' have descriptions. The text's mention of 'multiple webpages' and 'Markdown format' aligns with these parameters but adds no new semantic detail beyond what the schema already provides. The baseline of 3 applies.

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 states a specific verb ('Scrapes'), a resource ('multiple webpages'), and a distinctive feature ('in parallel') that sets it apart from the sibling tool 'scrape_url' which likely handles single URLs. It also clarifies the output format ('AI-readable Markdown') and a key capability ('access blocked sites through browser rendering').

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 description implies usage for multiple URLs and for sites that may be blocked, but it does not explicitly mention when to avoid using this tool or point to alternatives like 'scrape_url' for single pages. While context is clear, no direct comparison or exclusions are provided.

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