Skip to main content
Glama

adb_screenshot_compressed

Captures a full-resolution Android screenshot and returns its path, dimensions, file size, and a ready-to-run ImageMagick command for converting it to a smaller JPEG.

Instructions

Take a screenshot and pull the full-resolution PNG, plus metadata for client-side compression. Returns local file path, dimensions, file size, and a ready-to-run imagemagick command for converting to a smaller JPEG. (Android doesn't ship imagemagick, so the actual compression is post-processing — this tool sets up everything you need.)

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

Input Schema

NameRequiredDescriptionDefault
scaleNoScale factor (0.1-1.0, default 0.5). 0.5 = half resolution
deviceNoDevice serial
qualityNoJPEG quality (10-100, default 50). Lower = smaller file, more artifacts
filenameNoOutput filename (default: screenshot_compressed_<timestamp>.jpg)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description usefully discloses that the tool pulls a full-resolution PNG, writes a local file, returns path and file metadata, and does not itself perform the JPEG compression. It also identifies the ImageMagick dependency and explains why the command must run off the Android device, though it does not cover storage-location or overwrite behavior.

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 compact and front-loads the capture behavior, then efficiently lists the returned information and clarifies the post-processing requirement. Each sentence contributes useful operational detail without repetition.

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 four-parameter tool with no annotations or output schema, the description supplies the key workflow, outputs, and external compression dependency needed to avoid expecting an already-compressed result. Its main remaining gaps are sibling selection guidance and the relationship between the schema's compression-oriented parameters and the full-resolution PNG output.

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 the baseline is 3 even though the description adds no parameter-specific details. It does not clarify how scale, quality, and the JPG-oriented filename relate to the returned full-resolution PNG versus the suggested post-processing command.

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 clearly states the verb and resource: take a screenshot, pull the full-resolution PNG, and prepare metadata for client-side compression. The compression-setup workflow gives it some distinction from other screenshot siblings, but it does not explicitly differentiate itself from adb_screencap or adb_screenshot_baseline.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The references to client-side compression and producing a smaller JPEG imply the intended use case, while clarifying that compression itself is post-processing. However, there is no explicit guidance on when to choose this tool over another screenshot tool or when a plain screenshot would suffice.

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

Deploy Server

Other Tools