Skip to main content
Glama

adb_list_packages

List installed Android packages and filter by name, device, or type to identify system or third-party apps on a connected device.

Instructions

List installed packages. Supports filtering by name.

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

Input Schema

NameRequiredDescriptionDefault
typeNoShow all, system-only, or third-party-only packagesall
deviceNoDevice serial
filterNoFilter packages containing this string

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?

With no annotations supplied, the description carries the full disclosure burden and largely drops it. It never states what the response looks like (names only versus full package identifiers), whether a device serial is required, or what happens when the filter matches nothing.

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?

Two short, front-loaded sentences with no filler; the core action leads. The second sentence restates information already in the schema, which is minor redundancy rather than a clarity problem.

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?

For a simple, all-optional list tool with a fully documented schema, this is close to adequate. However, with no output schema and no annotations, the definition should say what the listing returns and whether device defaults are assumed.

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 coverage is 100%, so all three parameters are already documented, including the enum for type and the substring semantics of filter. The description's "filtering by name" merely echoes the filter parameter without adding syntax or behavioral detail, so the 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?

States a specific verb and resource ("List installed packages") that an agent can act on immediately. It does not distinguish itself from adjacent siblings such as adb_package_info, adb_list_splits, or adb_apex_list, so an agent must infer which listing tool applies.

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 use this versus adb_package_info or adb_apex_list, and no mention of prerequisites such as a connected device or authorization state. Usage is only implied by the tool name and the single filtering sentence.

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