Skip to main content
Glama

Get screenshot

get_screenshot
Read-only

Scrape a URL using ScrapingBee and return it's screenshot.

Scope: one URL per call, with the result returned into the conversation. For many URLs, a whole site, output written to a file or directory, resumable jobs, or a scheduled re-run, use the ScrapingBee CLI instead — scrapingbee scrape --input-file urls.txt --output-dir results, scrapingbee crawl URL --save-pattern ..., scrapingbee schedule --every. This server has no batch, crawl, file-output or scheduling equivalent.

Docs: https://www.scrapingbee.com/documentation/remote-mcp/

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the page to scrape.
waitNoMilliseconds to wait after page load (0–35000).
deviceNodesktop (default) or mobile.desktop
cookiesNoSemicolon-separated cookies to send to the target.
timeoutNoRequest timeout in milliseconds (1000–140000, default 140000).
wait_forNoCSS or XPath selector to wait for before returning.
render_jsNoWhether to use headless-browser rendering.
session_idNoInteger 0–10000000 to reuse an IP for up to 5 minutes.
js_scenarioNoStringified JSON object of browser interaction instructions.
country_codeNoISO 3166-1 alpha-2 country code (e.g. "fr", "us") to route the request through an IP in that country. Only takes effect when premium_proxy or stealth_proxy is True.
wait_browserNodomcontentloaded (default), load, networkidle0, networkidle2.domcontentloaded
window_widthNoViewport width (default 1920).
custom_googleNoSet to True if the url is a google domain in the following format: <subdomain>.google.<top-level-domain> (Example: translate.google.com, mail.google.com, www.google.co.in etc)
json_responseNoDeprecated, removed in Version 3. Return the full JSON envelope (page content plus the base64 image under its "screenshot" key) instead of the raw image.
premium_proxyNoWhether to use a premium proxy for the request. Use it only if you are getting blocked by the website, that is when you get a 500 status code.
stealth_proxyNoWhether to use a stealth proxy for the request. Use it only if you are getting blocked by the website while using premium_proxy, that is when you get a 500 status code.
window_heightNoViewport height (default 1080).
block_resourcesNoBlock images/CSS to speed up rendering.
screenshot_selectorNoA CSS selector to take a screenshot of a specific element.
screenshot_full_pageNoWhether to take a screenshot of the full page or just the viewport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuine behavioral context by stating the result lands in the conversation and that this server has no batch/crawl/file-output/scheduling capability. It does not disclose the response shape (raw image bytes versus a JSON envelope), which is precisely the thing an agent needs to know before calling a screenshot tool.

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 statement and the 'one URL per call' scope constraint are front-loaded, and the CLI escape hatch is clearly bracketed as out-of-scope. The three inline CLI examples are somewhat verbose for an agent that cannot invoke them, but they do crystallize which workloads are unsupported.

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?

For a 20-parameter tool with no output schema, the definition covers scope and out-of-scope workloads but never explains what actually comes back (image bytes vs. base64 vs. JSON envelope) or whether credits are consumed. Those are material omissions for a screenshot call with render_js, proxy, and viewport knobs.

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 all 20 parameters are already self-documenting, and baseline 3 applies. The description contributes no parameter-level meaning, though it does at least rule out passing many URLs to the url field.

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 names a specific verb and resource ('Scrape a URL ... return its screenshot'), and the screenshot outcome implicitly separates it from get_page_html/get_page_text siblings. It stops short of naming those siblings explicitly, so an agent must infer the contrast from a sibling list rather than the text.

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?

It gives unusually explicit negative guidance: one URL per call, no batch, no crawl, no file/directory output, no resumable jobs, no scheduling, with concrete CLI command alternatives for each. What's missing is guidance on when to pick this over the text/HTML siblings when the real goal is content rather than an image.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources