Skip to main content
Glama

screenshot_webpage

Browser-based webpage screenshot capture tool. Captures high-resolution JPEG or PNG screenshots of public webpages using isolated headless Chromium with configurable desktop/mobile viewport and optional full-page capture.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS URL of a webpage to capture as a screenshot.
scrollNoScroll down to trigger lazy-loaded content before capture.
wait_msNoOptional extra wait in milliseconds (0-5000) before capture.
viewportNoDevice viewport preset ('desktop' for 1280x800, 'mobile' for 390x844).desktop
full_pageNoCapture the full scrollable page height up to 4000px.
image_formatNoOutput image format ('jpeg' or 'png').jpeg
dismiss_cookiesNoAttempt to dismiss cookie/GDPR banners before capture.
wait_for_selectorNoOptional CSS selector to wait for before capture.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / dismiss_cookies
      Added value: +{
      +  "default": true,
      +  "description": "Attempt to dismiss cookie/GDPR banners before capture.",
      +  "title": "Dismiss Cookies",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / scroll
      Added value: +{
      +  "default": false,
      +  "description": "Scroll down to trigger lazy-loaded content before capture.",
      +  "title": "Scroll",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / wait_for_selector
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 256,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional CSS selector to wait for before capture.",
      +  "title": "Wait For Selector"
      +}
    • addedInput schema / properties / wait_ms
      Added value: +{
      +  "default": 0,
      +  "description": "Optional extra wait in milliseconds (0-5000) before capture.",
      +  "maximum": 5000,
      +  "minimum": 0,
      +  "title": "Wait Ms",
      +  "type": "integer"
      +}
  2. Added

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It discloses useful context — isolated headless Chromium session, viewport presets, optional full-page capture — but says nothing about what happens on unreachable or non-public URLs, whether there is a timeout/rate limit, how the image is returned, or what 'high-resolution' means in output terms. For a browser-automation tool with zero annotation coverage, these omissions matter.

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 tightly written sentences with the core action front-loaded and supporting detail (formats, engine, viewport, full-page) after it. The opening phrase 'Browser-based webpage screenshot capture tool' partially restates the tool name, which is the only wasted wording.

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 an 8-parameter tool with no output schema and no annotations, the description covers what the tool does but not what it returns (raw image bytes, a URL, base64?) or how failures surface. The schema fills in parameter detail, but the return contract and error behavior remain unaddressed, leaving a meaningful gap for an agent that must handle the result.

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 parameter including defaults, ranges (wait_ms 0-5000), and viewport presets is already documented in structured form. The description adds no parameter-level meaning beyond restating viewport and full-page capture, so the baseline 3 applies.

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 states a concrete verb and resource ('Captures high-resolution JPEG or PNG screenshots of public webpages') plus the implementation detail (isolated headless Chromium), which makes the operation unmistakable. It stops short of explicitly differentiating itself from near-neighbors like render_webpage or extract_webpage_text, so the agent must infer that this one produces an image rather than text or a rendered DOM.

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?

Usage is only implied: the word 'public' signals that authenticated or private pages are out of scope, which is a real constraint, but there is no explicit statement of when to choose this over fetch_webpage, render_webpage, or webpage_to_markdown. No exclusions, prerequisites, or alternative routing are provided, leaving the agent to infer selection from the tool name.

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.