MrScraper MCP Server

Official

by mrscraper-com

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Web Search

webSearch

Read-only

Search Google using query text or a search URL, returning parsed JSON or HTML results with region, language, page, JavaScript rendering, and timeout controls.

Instructions

Searches Google from query text or a Google search URL passed as url. Matches the Python SDK's web_search options. Set raw=false and format=json for parsed results; the SDK-compatible default raw=true returns HTML. Google URLs supply q, gl, hl, and start; explicit region, language, and page override URL-derived values. render_js enables dynamic features; timeout controls the local request deadline. Returns status_code, data, and sanitized headers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`raw`	No	SDK compatibility default: true requests HTML and overrides format. Set false for parsed JSON results.
`url`	Yes	Required search query text or complete Google search URL.
`page`	No	One-based result page; overrides the page derived from start in a Google URL.
`format`	No	Response representation when raw=false.	json
`region`	No	Country code; overrides gl from a Google search URL.
`timeout`	No	Local upstream HTTP deadline in seconds; omitted from the JSON body.
`language`	No	Language code; overrides hl from a Google search URL.
`render_js`	No	Render JavaScript-dependent search features.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Response body as parsed JSON or text.
`error`	No	Request failure message, if any.
`headers`	Yes	Response headers with credentials and cookies removed.
`status_code`	Yes	Upstream HTTP status, or null for a network failure.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Oct 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds important behavior beyond the annotations: the SDK-compatible raw=true default returns HTML, URL parameters are derived and can be overridden, render_js enables dynamic features, and timeout is a local deadline.

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 purpose is front-loaded and the remaining sentences are dense but useful. The only minor redundancy is the return-value sentence, since an output schema exists, but it remains short and harmless.

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 annotations, full schema description coverage, and an output schema, the description covers the call-critical behavior an agent needs: query vs URL input, raw/format behavior, override rules, JavaScript rendering, and timeout. Nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds useful cross-parameter semantics: raw overrides format, Google URLs supply q/gl/hl/start, explicit region/language/page override URL-derived values, and timeout is excluded from the JSON body.

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 precise verb and resource: 'Searches Google from query text or a Google search URL passed as url.' That clearly separates it from scraperAPI and status without needing to name them.

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?

It gives operational guidance such as setting raw=false and format=json for parsed results, but it does not explicitly say when to use this tool versus scraperAPI or status, nor when not to use it. Usage is implied rather than routed.

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

Deploy Server