Skip to main content
Glama
pim97

Scrappey MCP Server

by pim97

scrappey_request

Send HTTP requests with antibot bypass to access protected web content using methods like GET and POST, supporting proxies and captcha solving.

Instructions

Send an HTTP request using Scrappey with antibot bypass capabilities. Supports GET, POST, PUT, DELETE, PATCH methods.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cmdYesHTTP method to use
urlYesTarget URL to request
sessionNoSession ID for session persistence
postDataNoData to send with POST/PUT/PATCH requests
proxyNoProxy in format http://user:pass@ip:port. Leave blank to use built-in proxy.
proxyCountryNoRequest proxy from specific country (e.g., 'UnitedStates', 'Germany', 'UnitedKingdom')
premiumProxyNoUse premium residential-like proxies for better success rates
mobileProxyNoUse mobile carrier proxies
noProxyNoDisable proxy usage entirely
cloudflareBypassNoEnable Cloudflare-specific bypass
datadomeBypassNoEnable Datadome bypass using specialized solver
kasadaBypassNoEnable Kasada bypass
disableAntiBotNoDisable automatic antibot detection
automaticallySolveCaptchasNoAutomatically detect and solve captchas on the page
alwaysLoadNoAlways load specific captcha types: 'recaptcha', 'hcaptcha', 'turnstile'
cssSelectorNoExtract content matching this CSS selector
innerTextNoInclude inner text of page elements
includeImagesNoInclude all image URLs in the response
includeLinksNoInclude all link URLs in the response
screenshotNoCapture page screenshot
screenshotWidthNoScreenshot width in pixels
screenshotHeightNoScreenshot height in pixels
filterNoReturn only specified fields: 'response', 'cookies', 'statusCode', 'innerText', etc.
videoNoRecord browser session as video
pdfNoGenerate PDF of the page
interceptFetchRequestNoURL pattern to intercept and return response data
abortOnDetectionNoURL patterns to block (e.g., analytics, tracking scripts)
whitelistedDomainsNoOnly allow requests to these domains
blackListedDomainsNoBlock requests to these domains
blockCookieBannersNoAutomatically block cookie consent banners
customHeadersNoCustom HTTP headers to send
cookiesNoCookie string to set
cookiejarNoCookie jar array format
localStorageNoLocalStorage data to set
refererNoHTTP Referer header value
userAgentNoCustom user agent string
timeoutNoRequest timeout in milliseconds
retriesNoNumber of retry attempts on failure
fullPageLoadNoWait for full page load
listAllRedirectsNoTrack and return all redirect URLs
removeIframesNoRemove all iframes from page
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions 'antibot bypass capabilities,' it fails to describe critical behavioral traits: whether this is a read-only or destructive operation, authentication requirements, rate limits, error handling, or what the response format looks like. For a complex tool with 41 parameters, this is a significant gap in transparency.

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 extremely concise and front-loaded: a single sentence that captures the core functionality. Every word earns its place with no redundancy or unnecessary elaboration. This is an excellent example of efficient communication for a tool with extensive schema documentation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's high complexity (41 parameters, no output schema, no annotations), the description is insufficiently complete. It doesn't address what the tool returns, error conditions, performance characteristics, or how it integrates with sibling tools. While the schema covers parameters well, the description fails to provide the broader context needed for effective tool selection and invocation.

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 the schema already documents all 41 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain parameter relationships, default behaviors, or practical examples. The baseline score of 3 reflects adequate coverage through the schema alone, with no extra value from the description.

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 the tool's purpose: 'Send an HTTP request using Scrappey with antibot bypass capabilities. Supports GET, POST, PUT, DELETE, PATCH methods.' This specifies the verb ('Send an HTTP request'), resource ('using Scrappey'), and key capability ('antibot bypass'). However, it doesn't explicitly differentiate from sibling tools like 'scrappey_browser_action' or 'scrappey_create_session', which likely have overlapping web interaction functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions 'antibot bypass capabilities' but doesn't explain when this is needed compared to simpler HTTP requests or other sibling tools. There are no usage prerequisites, exclusions, or named alternatives provided, leaving the agent with minimal contextual direction.

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/pim97/mcp-server-scrappey'

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