Skip to main content
Glama

adb_ls

List files and directories on an Android device via ADB by specifying a path and device serial; enable detailed output to inspect storage contents.

Instructions

List files and directories on the device

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

Input Schema

NameRequiredDescriptionDefault
pathNoDirectory path on device/sdcard
deviceNoDevice serial
detailsNoShow detailed listing (ls -la)

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

C2.9/5.0
Behavior2/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. It implies a read-only operation but never says so, and it omits error behavior for a nonexistent path, whether the default is /sdcard, what permissions are needed, or what the returned listing looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short, front-loaded sentence with zero filler. It is efficient, though the terseness comes at the cost of the guidance covered in other dimensions rather than being a structural flaw.

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?

With only 3 fully-documented parameters and no output schema, the definition is functional but thin: it never indicates that listing is relative to a device path defaulting to /sdcard, nor how entries are returned. Adequate as a minimum-viable definition, not complete.

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 schema already documents path, device, and the details flag (including the 'ls -la' meaning). The description adds no extra meaning about defaults or format, so baseline 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 gives a specific verb ('List') and resource ('files and directories') plus a scope ('on the device'), so the agent knows exactly what the tool does. It does not, however, distinguish itself from nearby siblings such as adb_find, adb_file_stat, or adb_cat, so it falls short of a 5.

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 statement of when to use this instead of adb_find (pattern search), adb_file_stat (single-entry metadata), or adb_cat (read contents). The only implied usage is 'you want a directory listing', which the agent must infer from the name alone.

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