Skip to main content
Glama
getcustomaise

customaise

Official

take_screenshot

Capture browser tab screenshots without stealing focus. Save as PNG file or return inline, with optional full-page capture.

Instructions

Capture a screenshot of a browser tab without stealing focus from the user. Defaults to the visible viewport. Set fullPage: true to capture the entire scrollable page as one tall image. WRITES A FILE by default: the PNG is saved to filePath, or to an auto-generated path in the system temp directory when filePath is omitted, and this call returns that path rather than the image. If you have no filesystem tool, pass output: "inline" and the image is attached to this response instead, with nothing written to disk. For background tabs and full-page captures, Chrome briefly displays its standard yellow developer-tools notice at the top of the target tab during capture; it clears automatically when capture completes (typically under one second).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNoTab ID to screenshot. Defaults to the active tab.
outputNoWhere the full payload goes. "file" (default) writes it to filePath, or the system temp directory when filePath is omitted and returns a summary plus the path, which keeps a large payload out of your context window. "inline" writes nothing and returns the whole payload in this response. Use it when you have no filesystem tool to read the file with, such as a chat client. "auto" follows the CUSTOMAISE_MCP_OUTPUT environment variable, falling back to "file".
filePathNoLocal file path to save the screenshot. Auto-generates a temp path if omitted. Ignored when output is "inline".
fullPageNoIf true, capture the entire scrollable page (single tall PNG). If false or omitted, capture the visible viewport only.
Behavior5/5

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

Discloses side effects not inferable from annotations: writes a PNG file by default, returns a path rather than image bytes, and shows a transient Chrome devtools notice for background/full-page captures. This complements the readOnlyHint=false annotation rather than contradicting it.

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?

Front-loaded with the core purpose and focus-stealing constraint, then covers full-page capture, file behavior, inline fallback, and the transient notice. Each sentence adds distinct information and the length is proportionate to the tool's behavior.

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?

For a tool with no output schema, the description adequately covers return behavior in both output modes and the key side effect of writing to disk. Defaults such as active tab, visible viewport, and file output are specified either in the description or schema, so an agent has what it needs to call correctly.

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 already documents all parameters at 100% coverage, so the baseline is 3; the description adds useful behavior around filePath auto-generation and inline image attachment. It clarifies what output modes return without repeating schema syntax.

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 action (capture a screenshot), a resource (browser tab), and a notable constraint (without stealing focus). It is clearly distinct from sibling tab tools like reload_tab and close_tab, even though no alternative screenshot tool exists.

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?

Provides explicit selection guidance: default viewport vs fullPage: true, and file output vs inline output with the condition 'If you have no filesystem tool'. This tells an agent exactly when to use each mode.

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/getcustomaise/customaise-mcp'

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