Skip to main content
Glama

adb_multi_install

Installs an APK on selected or all connected Android devices in parallel, enabling batch app deployment without repeating installs device by device.

Instructions

Install an APK on multiple (or all) connected devices in parallel.

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": {
      "apkPath": "<apkPath>"
    },
    "name": "adb_multi_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
apkPathYesLocal filesystem path to the APK file
devicesNoDevice serials (omit for all online devices)
replaceNoReplace existing app (-r)

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.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and its only added trait is 'in parallel'. It does not disclose what happens on partial failure (does one device failing abort the rest?), whether the call blocks until all installs finish, what permissions or device states are required, or how results are aggregated. For a mutating multi-device tool this leaves significant gaps.

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 front-loaded sentence with no wasted words and the parallel/multi-device qualifier placed early. It is efficient, though the extreme brevity contributes to the missing failure and blocking semantics rather than compensating for them.

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

Completeness2/5

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

There are no annotations and no output schema, so the description is the only place an agent can learn behavioral expectations for a parallel mutation across N devices. It omits error semantics, partial-success handling, return shape, and ordering/blocking behavior, which are exactly the things an agent needs before invoking this over the simpler adb_install.

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 apkPath, devices, and replace (including the -r mapping and the omit-for-all default) are already fully documented in the schema. The description adds nothing beyond that, so the baseline of 3 is appropriate.

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 states a specific verb and resource (install an APK) plus scope (multiple or all connected devices, in parallel), which is enough to distinguish it from the single-device adb_install in the sibling list. It stops short of naming that sibling explicitly, so differentiation requires the agent to infer it from the name.

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?

'Multiple (or all) connected devices' implies the when-to-use case versus a single-device install, and the schema note 'omit for all online devices' reinforces it. However, there is no explicit statement of when to prefer this over adb_install, adb_install_bundle, or adb_farm_run, and no prerequisites such as requiring devices to be online.

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