Skip to main content
Glama

adb_extract_apks

Extract all APK splits for a specified Android package from a connected device to a local directory for analysis, backup, or transfer.

Instructions

Pull all APK splits for a package from the device to a local directory. Useful for analysis, backup, or transfer to another device.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "packageName": "<packageName>"
    },
    "name": "adb_extract_apks"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
outputDirNoLocal output directory (default: temp dir)
packageNameYesPackage name to extract

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.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the key trait that this writes files to the local filesystem and retrieves all splits rather than just the base APK. However, it says nothing about overwrite behavior for existing files, required permissions, or what happens if the package has no splits or is not installed.

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 compact sentences with the action stated first and the rationale second; nothing is redundant. The second sentence is somewhat generic but still earns its place by orienting the agent toward use cases.

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 three-parameter tool with no annotations and no output schema, the definition is adequate but thin: it never indicates what the tool returns (file paths? count?) or how partial failures are reported, which an agent needs to chain calls correctly.

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 device, outputDir, and packageName are already documented, including the temp-dir default. The description reinforces 'all APK splits' semantics for packageName but adds no format or constraint detail 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?

States a specific verb and resource: pulling all APK splits for a named package from the device to a local directory. This is clearly distinguishable from adb_list_splits or adb_pull in intent, though the description never names those siblings to reinforce the distinction.

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 second sentence lists intended use cases (analysis, backup, transfer) which implies when to reach for it, but there is no explicit when-not guidance and no pointer to alternatives such as adb_list_splits for enumeration-only or adb_pull for single-file retrieval.

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