Skip to main content
Glama

capture_page

Read-onlyIdempotent

Capture screenshots or PDFs of a web page or specific element, saving them to disk or returning them inline for visual checks and documentation.

Instructions

Screenshot (png/jpeg) or PDF of the page or an element, saved under cwd or TURBO_BROWSER_SAVE_ROOT; optional inline image.

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_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
modeNoscreenshot
textNo
typeNopng
scaleNocss
tabIdNo
qualityNo
frameIdxNo
fullPageNo
savePathNo
selectorNo
returnImageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: files are written under cwd or TURBO_BROWSER_SAVE_ROOT, and an inline image can optionally be returned. It does not explain how savePath interacts with the default root, how returnImage changes the response, or what happens with quality/scale.

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 compact, front-loaded sentence with the action and formats first and the storage location second; no filler. Density comes at the cost of jargon like 'cwd' and 'TURBO_BROWSER_SAVE_ROOT' that a calling agent may not resolve.

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

Completeness2/5

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

With 12 parameters, zero schema descriptions and no output schema, the description is too thin for the tool's complexity. An agent still cannot determine how to choose between ref and selector, what scale/quality/fullPage do, or how the returned payload differs when returnImage is set.

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 description coverage is 0% across 12 parameters, so the description carries the full burden. It only implicitly touches mode, type, selector/ref, savePath and returnImage, and leaves ref-vs-selector distinction, scale, quality, fullPage, tabId, frameIdx and text entirely undefined.

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?

States a specific verb+resource: capture a screenshot (png/jpeg) or PDF of the page or an element. The output formats and target scope are named, so an agent can tell it apart from text-extraction or diagnostics siblings without opening the schema. It stops short of naming an explicit alternative, which keeps it at 4 rather than 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 when-to-use or when-not-to-use guidance: nothing says when to choose pdf vs screenshot, when to target an element vs the full page, or when to prefer extract_clean_text or page_diagnostics. The phrase 'optional inline image' hints at a return-vs-save choice but never states the tradeoff.

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