Skip to main content
Glama

kadi_bence/website-screenshot

kadi_bence--website-screenshot
Destructive

This tool calls the Actor "kadi_bence/website-screenshot" and retrieves its output results. Actor description: $2.50 per 1,000 screenshots, failed pages free. Capture screenshots or PDFs of web pages. Input: URLs; format (PNG, JPEG, WebP, PDF), full page or viewport, device preset, element selector, dark mode. Returns per URL: file URL, title, HTTP status, size. Hides cookie banners, loads lazy images.

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": {
      "urls": "<urls>"
    },
    "name": "kadi_bence--website-screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes**REQUIRED** Web pages to capture, one per line, e.g. https://example.com/pricing or just example.com (https:// is added). Duplicates are skipped, max 50,000 per run. You can paste a CSV column. Only capture pages you are allowed to. Example values: ["https://example.com","https://apify.com","https://www.wikipedia.org"]
deviceNoDesktop 1920x1080, Laptop 1366x768, Tablet 820x1180 (2x pixels, touch, mobile user agent), Mobile 412x915 (2x pixels, touch, Android Chrome user agent). Sites that serve a mobile layout will show it. Example values: "desktop"desktop
formatNoPNG = lossless, sharp text. JPEG / WebP = much smaller files (WebP smallest). PDF = printable document with selectable text. Every format costs the same. Example values: "png"png
delayMsNoExtra wait after loading, e.g. 2000 for pages with intro animations or slow charts. Max 30000.
qualityNoJPEG and WebP quality, 1-100, e.g. 70 for small thumbnails. Higher = sharper but bigger files. Ignored for PNG and PDF. Example values: 80
blockAdsNoBlocks requests to common ad and tracking networks and hides empty ad slots. Faster loads and cleaner screenshots. Example values: true
darkModeNoTell the page the visitor prefers a dark color scheme (prefers-color-scheme: dark). Works on sites that support dark mode.
fullPageNoOn: the whole scrollable page. Off: only the visible viewport ("above the fold"). Ignored for PDF and when a CSS selector is set. Example values: true
selectorNoOptional. Capture only the first visible element matching this CSS selector, e.g. #pricing, .hero or table.results. If nothing matches, the row is an error and is not charged.
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
pdfFormatNoPaper size for PDF output, e.g. A4 (Europe) or Letter (US). Example values: "A4"A4
pdfMarginNoMargin on all four sides, e.g. 10mm, 0.5in, 1cm, 20px or 0. Example values: "10mm"10mm
waitUntilNoLoad = page load event (max 8 s after the page is ready) plus up to 1.5 s for late network requests (good default). Network idle = wait until the network is quiet (up to 15 s; slower but safer for single-page apps). DOM ready = fastest, may miss images. Example values: "load"load
maxRetriesNoRetries after a timeout, network error or tab crash (HTTP errors like 404 are not retried). Failed pages are not charged. Example values: 1
pdfLandscapeNoLandscape instead of portrait PDF pages. Useful for wide dashboards and tables.
scrollToLoadNoScrolls through the page (max 8 s) before a full-page, element or PDF capture so lazy-loaded images and sections render, then scrolls back to the top. Example values: true
hideSelectorsNoOptional. Extra elements to hide before capture (up to 50), e.g. chat widgets or newsletter pop-ups: #intercom-container, .newsletter-modal
viewportWidthNoOverrides the device width (200-3840), e.g. 1280. Leave empty to use the device preset.
maxConcurrencyNoHow many pages are captured at the same time. 0 = automatic from the run memory (2 GB: 3 tabs, 4 GB: 6, 8 GB: 12). For more speed, give the run more memory: the price per screenshot stays the same.
viewportHeightNoOverrides the device height (200-4320), e.g. 800. For viewport screenshots this is the image height.
pdfUseScreenCssNoOn: the PDF uses the page's normal screen styles (looks like the website). Off: the page's print stylesheet is used (often plainer, without navigation). Example values: true
waitForSelectorNoOptional. Wait until this element is visible before capturing (max 15 s), e.g. .chart-loaded. If it never appears, the row is an error and is not charged.
respectRobotsTxtNoSkip pages that the site's robots.txt does not allow for automated access (RFC 9309). Skipped pages are listed and not charged. Keep this on unless you own the site. Example values: true
deviceScaleFactorNo1 = normal, 2 = retina (twice the pixels in each direction), 3 = extra sharp. Empty = device default (desktop 1, tablet and mobile 2). Bigger images take longer.
fullPageMaxHeightNoVery long or infinite-scroll pages are cut at this height (CSS pixels) and the row gets truncated: true. WebP is also limited to 16,383 px and JPEG to 65,500 px (divided by the pixel density). Example values: 20000
hideCookieBannersNoHides consent pop-ups from 35+ consent tools (OneTrust, Cookiebot, Didomi, Usercentrics, Quantcast...) and other cookie overlays with CSS. Nothing is clicked: no consent is given on your behalf. Example values: true
pdfPrintBackgroundNoKeep background colors and images in the PDF (as on screen). Example values: true
proxyConfigurationNoUsually not needed. Use Apify Proxy (datacenter) to capture from other IP addresses. Residential proxies are not supported. Example values: {"useApifyProxy":false}
navigationTimeoutSecsNoGive up on a page that does not load within this time (it is retried once). Failed pages are not charged. Example values: 45

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "bytes": {
      +      "type": "number"
      +    },
      +    "cookieBannersHidden": {
      +      "type": "number"
      +    },
      +    "device": {
      +      "type": "string"
      +    },
      +    "durationMs": {
      +      "type": "number"
      +    },
      +    "error": {
      +      "type": "null"
      +    },
      +    "finalUrl": {
      +      "type": "string"
      +    },
      +    "format": {
      +      "type": "string"
      +    },
      +    "fullPage": {
      +      "type": "boolean"
      +    },
      +    "height": {
      +      "type": "number"
      +    },
      +    "key": {
      +      "type": "string"
      +    },
      +    "pdfPages": {
      +      "type": "null"
      +    },
      +    "screenshotUrl": {
      +      "type": "string"
      +    },
      +    "selector": {
      +      "type": "null"
      +    },
      +    "status": {
      +      "type": "number"
      +    },
      +    "takenAt": {
      +      "type": "string"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "width": {
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true) already carry the safety profile, and the description adds genuinely useful context beyond them: pricing ($2.50 per 1,000 screenshots, failed pages free), what is returned per URL (file URL, title, HTTP status, size), and that nothing is clicked and no consent is given. The cost and failure-charging semantics are exactly the kind of detail an agent needs before firing a run. The description does not itself mention the destructive/open-world profile, and there is mild tension between 'nothing is clicked' and the destructiveHint annotation, but this is a nuance rather than a direct contradiction.

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?

Two sentences with no padding: the wrapper sentence frames the Actor call and the actor description is front-loaded with price, capability, inputs and returns. It is dense but every clause carries information an agent can use.

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 output schema and full parameter coverage mean returns and inputs need not be re-explained, and the description covers purpose, cost and failure handling. However, with 29 parameters and polling behavior baked in via waitSecs, the definition omits any guidance on long-running runs, polling with get-actor-run, or choosing among the sibling tools.

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 29 parameters in detail, and baseline is 3. The description only recaps a subset (format, full page or viewport, device preset, element selector, dark mode) and adds no semantics beyond what the schema states, such as interactions between selector, fullPage and PDF options.

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 gives a specific verb+resource ('Capture screenshots or PDFs of web pages') plus the output formats and returned fields, so the agent knows exactly what the tool does. It never differentiates itself from sibling tools such as pagespeed-checker or seo-site-audit, which is the only thing keeping it off 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 Guidelines2/5

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

There is no statement of when to choose this tool versus the many sibling capture/audit tools, and no stated prerequisites beyond a passing 'Only capture pages you are allowed to.' The input hints (format, device, selector, dark mode) describe configuration, not when-to-use guidance.

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.