Skip to main content
Glama

capture_screenshot

Capture viewport, full-page, or element screenshots and save them with metadata to an output directory for responsive layout testing and visual verification.

Instructions

Capture a viewport, full-page, or specific element screenshot and save it to the output directory with metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "capture_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoScreenshot type: "viewport", "fullPage", or "element" (default: "viewport").
widthNoOptional custom viewport width in px.
heightNoOptional custom viewport height in px.
selectorNoCSS selector (required when type is "element").
filename_prefixNoPrefix for saved screenshot filename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It mentions saving to an 'output directory with metadata' but does not say where that directory is, what metadata accompanies the file, the returned value format, whether files are overwritten, or whether a browser session must already exist—significant gaps for a capture-and-write 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?

One sentence, front-loaded with the verb and the three modes; it is efficient, though the trailing 'save it to the output directory with metadata' packs unexplained behavior into the same clause.

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 five-parameter capture tool with no annotations and no output schema, the description is only minimally adequate. An agent knows what it does and which modes exist, but not the return shape, output location, or prerequisite page state.

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 explains type, width, height, selector, and filename_prefix. The description adds only the enumeration of screenshot types, which is redundant with the enum, and says nothing about how width/height interact with fullPage or element modes.

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 (capture) and resource (screenshot) and enumerates the three supported modes (viewport, full-page, element) that match the schema enum. It does not explicitly differentiate itself from siblings like compare_viewports or inspect_element_responsiveness, so it stops short of 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 guidance on when to pick this tool over siblings (e.g., compare_viewports, inspect_element_responsiveness), and no prerequisites such as needing a page opened first via open_page. The only usage-shaped signal is the parenthetical that selector is required for element type.

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