Skip to main content
Glama

take_screenshot

Capture the full screen, a specific app window (even in the background), or a user-selected region as an image. Supports annotations and saves to a file or clipboard.

Instructions

Capture the screen and return the image so it can be looked at. mode 'screen' captures everything (no user interaction); mode 'app' captures one named window and needs no user interaction either — pass 'app' and/or 'title_contains', and it works even when that window is behind others, minimized excepted, without raising it or taking focus; 'region' and 'window' hand the user the native crosshair/window picker and wait for them. Prefer 'app' whenever the user asks about a particular program ("what is playing in Spotify", "read the error in Xcode") — it is the only mode that can see a window the user cannot, and it does not disturb their desktop. Set annotate=true to open Plonk's drawing editor on the capture instead of returning it — use that when the user wants to mark the shot up themselves. Optional 'path' writes to an explicit file, otherwise the configured screenshot folder is used; 'clipboard' overrides the configured copy-to-clipboard behavior. The returned image is scaled down for legibility; the file at 'path' keeps full resolution. To draw on the result, pass that 'path' to annotate_screenshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNomode 'app': app name or bundle id, case-insensitive substring (e.g. 'Spotify')
modeNoscreen
pathNoExplicit output file path (.png)
annotateNoOpen the annotation editor instead of returning the image
clipboardNoAlso copy the capture to the clipboard
include_imageNoReturn the image content itself, so it can be inspected (default true)
title_containsNomode 'app': narrows to a window whose title contains this, for an app with several
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It thoroughly discloses behavior: modes that need no interaction, app mode working behind other windows without focus, scaled-down returned image, full-resolution file, clipboard override, and annotation editor behavior. This level of detail is exceptional.

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?

The description is dense but each sentence earns its place. It front-loads the core purpose, then systematically explains modes, usage preferences, and options without redundancy. The structure is logical and scannable.

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 7 parameters and no output schema, the description is remarkably complete. It covers all mode behaviors, user interaction requirements, output image scaling, file resolution, clipboard behavior, and how to hand off to annotate_screenshot. There are no major gaps.

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

Parameters5/5

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

Even with high schema coverage, the description adds substantial meaning: explains mode semantics in depth, how app/title_contains work together, the effect of path and clipboard, and what annotate=true changes. It clarifies the return image scaling in relation to include_image, adding value beyond the schema.

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 starts with a clear verb+resource: 'Capture the screen and return the image so it can be looked at.' It goes on to explain the different capture modes and even references the sibling tool annotate_screenshot, explicitly differentiating it from this tool.

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 guidance: 'Prefer 'app' whenever the user asks about a particular program' with rationale, and explains when to use annotate=true. Also clarifies that 'region' and 'window' modes require user interaction, helping the agent choose appropriately.

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/ostapondo/Plonk'

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