serper-search-mcp-server

scrape

Fetch and extract full page content from one URL as markdown or plain text to read a promising search result in full.

Instructions

Fetch and extract the full contents of a single URL via Serper Scrape API. Returns the page content as markdown (or plain text). Use after a search to read a promising page in full. Costs ~2 credits per page.

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

Input Schema

Name	Required	Description
`url`	Yes	Absolute URL of the page to scrape (http/https).
`max_chars`	No	Truncate returned content to this many characters (1000–200000). Default: 50000.
`include_links`	No	Include links found on the page. Default: false.
`include_images`	No	Include image URLs found on the page. Default: false.
`include_videos`	No	Include videos found on the page. Default: false.
`include_markdown`	No	Return a markdown rendering of the page. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.1Nov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does add real value: it discloses the return format (markdown or plain text) and the approximate cost (~2 credits per page), neither of which is in the schema. It omits failure modes such as paywalled or JS-rendered pages and any rate-limit or auth details, which keeps it from a 5.

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?

Three short sentences, front-loaded with the action and resource, then return format, then usage context and cost. No filler or redundancy.

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 six-parameter read tool with full schema coverage and no output schema, the description covers what it does, what it returns, when to reach for it, and its cost. Missing edge-case behavior (blocked pages, empty extractions, whether content is truncated) is the only notable gap.

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%, so every one of the six parameters is already documented with defaults and ranges in the schema. The description adds nothing beyond that baseline, so a 3 is the appropriate ceiling here.

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?

"Fetch and extract the full contents of a single URL via Serper Scrape API" gives a specific verb (fetch/extract) and resource (single URL's full contents), and the single-URL scope cleanly separates it from the multiple search_* siblings that only surface result snippets.

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?

"Use after a search to read a promising page in full" gives a concrete when-to-use signal tied to the search tools in the sibling set. It stops short of stating when not to use it (e.g. batch fetching, or pages already covered by search_rag_context), so it is clear but not exhaustive.

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

Deploy Server