Skip to main content
Glama

adb_install_bundle

Install an app bundle by pushing all split APKs—base plus language, density, and ABI configs—to an Android device with a single install-multiple command.

Instructions

Install multiple APK splits (app bundle) on the device using install-multiple. Provide all split APK files — base APK plus config splits (language, density, ABI).

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": {
      "apkPaths": "<apkPaths>"
    },
    "name": "adb_install_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
replaceNoReplace existing app (-r)
apkPathsYesArray of local paths to split APK files (base + config splits)
allowDowngradeNoAllow version downgrade (-d)

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?

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the underlying 'install-multiple' mechanism and the completeness requirement for split sets, which is genuinely useful. It does not mention failure modes (INSTALL_FAILED_* errors, missing split rejection), overwrite behavior beyond the schema's 'replace' flag, or that the device must be online.

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 sentences, front-loaded with the action and mechanism, with no filler. The second sentence is a useful constraint rather than padding.

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 mutating install tool with no annotations and no output schema, the description covers what it does and what inputs must look like, but leaves the agent without error-handling context or safety/permission notes. It is adequate but not complete for a state-changing operation.

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 all four parameters are already documented in the schema, establishing a baseline of 3. The description's note about base APK plus config splits (language, density, ABI) restates and slightly enriches the apkPaths semantics, but adds nothing about device, replace, or allowDowngrade.

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 and resource ('Install multiple APK splits (app bundle)') and names the underlying adb mechanism ('install-multiple'), which clearly separates it from the single-APK adb_install sibling. It stops short of naming that sibling explicitly, so the differentiation is implied rather than stated.

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?

Usage context is implied by the parenthetical '(app bundle)' and the instruction to supply base plus config splits, which tells an agent this is for split-APK scenarios rather than plain installs. However, there is no explicit when-to-use / when-not guidance and no reference to alternatives such as adb_install or adb_multi_install.

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