Skip to main content
Glama

adb_screencap

Captures an Android device screenshot, saves it to the local filesystem, and returns the saved file path.

Instructions

Take a screenshot and save to local filesystem. Returns the file path.

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_screencap"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
filenameNoOutput filename (default: screenshot_<timestamp>.png)

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

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It does say the capture is written to the local filesystem and returns a file path, which tells the agent the side effect is a local write rather than a device write. It omits the device-selection behavior when no serial is supplied, whether existing files are overwritten, and any permission or size caveats.

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?

Two short sentences, both of which earn their place: the first states the action and destination, the second states the return value. The key fact, saving to the local filesystem, is front-loaded with no filler.

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

Completeness3/5

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

The description covers the core action, side effect, and return value for a two-parameter tool with no output schema. It leaves a gap on routing among the numerous screenshot siblings and on default-device behavior, which matters for an agent picking a capture tool.

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 both parameters (device serial, filename with its timestamp default) are already documented. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 and resource: take a screenshot and save it to the local filesystem, with the return value stated. It is clear what the tool does, but it offers no differentiation from the many sibling screenshot tools (adb_screencap_annotated, adb_screenshot_compressed, adb_screen, adb_screenshot_baseline, adb_snapshot_capture).

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 guidance on when to choose this tool over the crowded set of screenshot siblings. The agent gets no condition or exclusion, such as when to use adb_screencap_annotated for UI-element overlays or adb_screenshot_compressed for size-constrained captures.

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