Skip to main content
Glama

pilot_screenshot

Take a PNG screenshot of a webpage or specific element, saving it to disk with support for full page, viewport, element ref, and clip region.

Instructions

Take a PNG screenshot of the current page or a specific element. Use when the user wants to capture what the page looks like visually, save a screenshot to disk, or capture a specific element's appearance. For a visual debug overlay with ref labels, use pilot_annotated_screenshot instead.

Parameters:

  • ref: Element reference from snapshot (e.g., "@e3") or CSS selector to screenshot a specific element (omit for full page)

  • full_page: Set to false for viewport-only capture (default: true, captures the entire scrollable page)

  • output_path: File path to save the screenshot (default: /tmp/pilot-screenshot.png). Must be within the allowed output directory

  • clip: Crop region as {x, y, width, height} pixel coordinates for a specific area of the page

Returns: The screenshot as a base64 PNG image and the file path where it was saved.

Errors:

  • "Output path must be within ...": The path is outside the allowed directory. Set PILOT_OUTPUT_DIR or use /tmp.

  • "Element not found": The ref is stale. Run pilot_snapshot to get fresh refs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoElement ref or CSS selector to screenshot
full_pageNoCapture full page (default: true)
output_pathNoOutput file path
clipNoClip region {x, y, width, height}
Behavior4/5

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

Discloses that the tool captures a PNG screenshot, defaults to full page, saves to disk, and returns base64 and file path. Includes common errors and their resolutions. However, no annotations exist, and the description could mention potential side effects or prerequisites (e.g., page must be loaded).

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?

Concise yet comprehensive: two sentences cover purpose and alternatives, followed by clear parameter descriptions and error handling. No unnecessary words.

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

Completeness5/5

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

Despite no output schema, the description explains return values (base64 PNG and file path) and common errors. All four parameters are well-documented. Completeness is high for a screenshot tool with clear side effects.

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

Parameters4/5

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

Schema description coverage is 100%, but the description adds value beyond schema by clarifying ref types (element ref vs CSS selector), full_page behavior (viewport-only vs scrollable), output_path constraints (allowed directory), and clip format (pixel coordinates).

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?

The description clearly states the tool's purpose: 'Take a PNG screenshot of the current page or a specific element.' It distinguishes from the sibling pilot_annotated_screenshot by directing users to use that tool for debug overlays.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides usage guidelines: 'Use when the user wants to capture what the page looks like visually, save a screenshot to disk, or capture a specific element's appearance.' Also mentions when not to use (pilot_annotated_screenshot for debug overlay) and includes error messages that guide user actions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TacosyHorchata/Pilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server