Skip to main content
Glama

Capture Website Screenshot

capture_url

Capture a web page screenshot as an image and save it to a file for use with design analysis, recreation, or reimagining tools. Specify URL, viewport size, mobile emulation, or full-page capture.

Instructions

Take a screenshot of a web page and return it as an image. It is also saved to a file whose path you can pass to analyze_design, recreate, reimagine and the other vision tools. Needs Google Chrome installed, or Chromium via npx playwright-core install chromium.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL (http or https)
widthNo
heightNo
mobileNoEmulate a 390px-wide phone
full_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does well on two points: it writes a file to disk as a side effect and it requires Chrome or Chromium installed (optionally via npx playwright-core install chromium). It omits where the file is written, whether it waits for page load, and how capture failures surface, so a mutation-adjacent tool with zero annotation coverage remains only partly transparent.

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?

Two short sentences, front-loaded with the core action, then the downstream handoff and prerequisite. Nothing is padded or redundant.

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

Completeness4/5

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

No output schema exists, but the description compensates by stating that an image is returned and a file path is produced. Prerequisites are covered. The remaining gap is the undocumented width/height/full_page parameters, which matters for a 5-parameter tool but is a modest omission overall.

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

Parameters2/5

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

Schema coverage is only 40% — url and mobile are documented in the schema, but width, height, and full_page have no descriptions anywhere. The description adds no parameter meaning at all (no viewport behavior, no full_page semantics), so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Take a screenshot of a web page') plus the return form ('return it as an image'), and clarifies its role as the upstream capture step for analyze_design, recreate, reimagine and other vision tools, which separates it from every sibling in the list.

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?

The description explains the downstream workflow explicitly — the saved file path is meant to be passed to the vision tools — which tells an agent when this tool is the right first step. It also states the Chrome/Chromium prerequisite, but gives no exclusions or failure guidance (e.g. pages that block headless capture, timeouts).

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