Skip to main content
Glama

capture_page

Capture authentic screenshots in an isolated browser with masked private fields, blocked third-party requests, and optional recorded interactions.

Instructions

Capture authentic screenshot in isolated browser; fields/private elements masked and third-party requests blocked.

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>",
      "output": "<output>"
    },
    "name": "capture_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
widthNo
heightNo
outputYes
recordNo
actionsNo
fullPageNo
recordFpsNo
showCursorNo
recordMaxSecondsNo
waitMillisecondsNo
allowInteractionsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds substantive behavior beyond them — masking of fields and private elements, blocking of third-party requests, and an isolated browser context. It still does not disclose side effects such as where the artifact is written, timeouts, or how long a capture with actions/recording may take.

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?

A single front-loaded clause packs the verb, the resource, the environment, and two safety behaviors with no filler. However, the extreme brevity leaves no structure for the many behavioral knobs, so density comes at the cost of coverage rather than being optimally sized.

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?

This is a complex tool (12 params including a 30-item polymorphic action array, video recording flags, and interaction toggles) with zero schema descriptions, so the description carries a heavy burden and delivers almost nothing about how to drive it. The presence of an output schema covers return values, but the input side is essentially undisclosed.

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, and the description mentions none of them — not url, output, width/height, fullPage, or the actions/wait/record family. The one partial tie-in ("fields/private elements masked") has no corresponding parameter, so an agent gets no help understanding the action sequence, recording options, or interaction toggles from the prose.

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?

Names a specific verb and resource ("Capture authentic screenshot") plus the execution context ("isolated browser"), which tells an agent what it gets back. It does not explicitly differentiate itself from siblings like capture_responsive_screens or capture_user_flow, so the boundary between single-shot capture and the multi-view/flow variants is left implicit.

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 and no alternative is named, despite five capture-related siblings. The phrase "in isolated browser" hints that this is for clean, repeatable captures, but the agent must infer when to pick this over capture_responsive_screens or capture_user_flow.

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