Skip to main content
Glama

list_screenshots

Retrieve all logged screenshots with their captions in sequence to review activity, QA evidence, or lab documentation.

Instructions

List every logged screenshot with its caption, in order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_screenshots"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. "List" plus "logged" implies a safe read-only retrieval and the text discloses the return contents (caption) and ordering, but says nothing about pagination, volume limits, or whether the log can be empty.

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?

A single ten-word sentence with zero waste, front-loading the verb and resource before the returned fields and ordering. Nothing could be removed without losing information.

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

Completeness4/5

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

For a zero-parameter tool with an output schema documenting return values, the description needs only to state scope and contents, which it does. The remaining gap is routing guidance against sibling listers such as pull_remote_screenshots.

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?

The tool takes zero parameters, which is the baseline-4 case; there is no parameter meaning for the description to explain. Schema coverage is 100% and the empty object schema is consistent with a no-argument lister.

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?

The description names a specific verb ("List") and resource ("logged screenshot") and states what each result carries (its caption) and the ordering. It implies local logged screenshots as distinct from remote ones, but never explicitly names pull_remote_screenshots or list_windows as alternatives.

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 guidance, no statement of when to prefer pull_remote_screenshots or list_windows, and no prerequisites or exclusions. The only implied guidance is that this returns everything logged, which an agent could infer from "every".

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