Skip to main content
Glama

app_screenshot

Captures a JPEG screenshot of the app screen or window for visual and layout questions, optionally saving to a file path or capturing full scrollable content as one tall image.

Instructions

JPEG screenshot of the app. Use only for visual/layout questions; app_snapshot is cheaper for finding elements. With saveTo, writes the file and returns only its path (no image tokens).

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": "app_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoauto (default) = visible screen; window = whole window incl. overlays
saveToNofile path (.jpg) to save instead of returning the image
qualityNo0-1, default 0.6
maxWidthNopixels, default 400
fullScrollNocapture the whole content of the main scroll view as one tall image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose the two behaviors that matter: the return is an image that costs image tokens, and saveTo changes the response shape to a path only while writing a file as a side effect. It stops short of stating read-only/no-mutation guarantees or what the capture may omit (e.g. hidden overlays), which keeps it at 4 rather than 5.

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?

Three compact clauses, front-loaded with the output format, then the routing rule, then the cheap-path option. No filler, no restatement of the tool name.

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 5-parameter, all-optional capture tool with no annotations and no output schema, the description covers cost, routing, and the saveTo response-shape switch, which is enough to call it correctly. Minor gaps remain around default behavior when area/fullScroll interact and around the absence of any mutation, but nothing blocking.

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

Parameters3/5

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

Schema description coverage is 100%, so area, saveTo, quality, maxWidth and fullScroll are already documented. The description adds one genuinely new piece of meaning for saveTo (no image tokens are consumed), but says nothing about area, quality, maxWidth or fullScroll, so the baseline of 3 applies.

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 verb and resource ("JPEG screenshot of the app") and immediately differentiates itself from the sibling app_snapshot by naming which questions each serves. An agent can pick between them without opening either schema.

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?

Explicit when-to-use ("Use only for visual/layout questions") plus the alternative and its selection criterion ("app_snapshot is cheaper for finding elements"). It even adds a second routing condition via saveTo, which avoids image tokens when only a file is needed.

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