Scrapi MCP Server

scrape_url

Scrape any webpage to Markdown or plain text, using browser rendering to access blocked sites.

Instructions

Scrapes a webpage 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": {
      "url": "<url>"
    },
    "name": "scrape_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The URL of the webpage to scrape
`format`	No	Output format: markdown (default) or text	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0May 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

There are no annotations, so the description must carry the full burden. It discloses that the tool uses browser rendering to access blocked sites, which is a useful behavioral detail. However, it doesn't mention potential limitations, rate limits, or error behavior, so transparency is incomplete.

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, with the primary purpose stated first and the key capability (browser rendering for blocked sites) as a secondary note. Every sentence is informative and there is no redundancy.

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?

The description covers the core function and a differentiator, but it misses the distinction from scrape_urls, which could lead to agent confusion. Since there is no output schema, the description does mention the return format sufficiently. Overall, it's adequate but with clear gaps.

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?

The schema already provides descriptions for both parameters (url and format), and the context signal indicates 100% schema description coverage. The tool description doesn't add significant parameter-level meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it scrapes a webpage and returns content in Markdown format, which is specific and action-oriented. However, it doesn't differentiate from the sibling tool scrape_urls, which likely handles multiple URLs, so it falls short of a 5.

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 mentions the ability to access blocked sites through browser rendering, which gives some context for when this tool might be preferred. However, it doesn't explicitly state when to use this tool versus alternatives like scrape_urls, so the guidance is implied rather than explicit.

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

Deploy Server