Skip to main content
Glama

screenshot_query

Find and re-open specific screenshots from cache by filtering on tag, window, or time, avoiding redundant re-captures.

Instructions

List screenshots already saved in the disk-cache WITHOUT re-reading any pixels. The screenshot tools return each capture as a cheap by-ref link (screenshot://by-ref/{captureId}); this lists what is in the cache — captureId + by-ref uri, dimensions, size in bytes, timestamp, and tag/window — so you can find and re-open a specific earlier capture, or check how much the cache holds before reclaiming space with screenshot_gc. The response also carries whole-cache totals (totalCaptures / totalBytes). Reading a capture's bytes still costs tokens, so open a by-ref link only when you actually need to inspect the pixels. Filter by tag (case-insensitive) / windowUuid / since / until; page with limit (default 50) and offset. Results are newest-first and never include a filesystem path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter to captures stored under this tag (case-insensitive). Omit to list all.
limitNoMaximum rows to return, newest first (default 50, max 500).
sinceNoOnly captures taken at/after this time (epoch milliseconds, inclusive).
untilNoOnly captures taken at/before this time (epoch milliseconds, inclusive).
offsetNoRows to skip from the newest end, for paging (default 0).
includeNoOptional response-shape opt-in. `['envelope']` returns the self-documenting envelope (`_version` / `data` / `as_of` / `confidence`). `['raw']` forces raw shape (overrides DESKTOP_TOUCH_ENVELOPE=1 server default). Default behaviour is raw shape (compat with existing clients).
windowUuidNoFilter to captures of a specific window (the window's stable id).
Behavior5/5

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

With no annotations, description fully discloses non-destructive behavior (no pixel read), response fields, ordering (newest-first), and a critical warning about token costs for reading bytes. No contradictions.

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?

Compact ~120 words, front-loaded with core purpose and key differentiators ('WITHOUT re-reading'). Each sentence adds unique value, no fluff. Structured logically from behavior to filtering to caveats.

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, description enumerates response fields (captureId, uri, dimensions, size, timestamp, tag/window, cache totals) and covers all relevant aspects: behavior, filtering, pagination, ordering, and token-warning. Complete for a list operation.

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 covers 100% of parameters, so baseline is 3. Description adds value by specifying filter semantics (case-insensitive tag, epoch ms timestamps), default/limits (limit 50 max 500, offset 0), and response shape opt-in, which go beyond schema alone.

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 lists screenshots from disk-cache without re-reading pixels, contrasting with sibling screenshot (capture) and screenshot_gc (reclaim space). It precisely describes the action and resource.

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 tells when to use (find/re-open captures, check cache, decide GC) and when not to (avoid opening by-ref links unless needed due to token cost). Mentions alternative screenshot_gc for reclaiming space.

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/wangkang1133/desktop-touch-mcp'

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